| 2 |
Approval of the agenda |
|
| R4-2218000 |
RAN4#104-bis-e Meeting Report |
ETSI MCC |
| R4-2218001 |
Agenda for RAN4 #105 |
RAN4 Chair (Huawei) |
| R4-2218002 |
RAN4#105 Meeting Arrangements and Guidelines |
RAN4 Chair (Huawei) |
| 3.1 |
Incoming liaison statement |
|
| R4-2218003 |
Reply LS on CCA configurations of neighbour cells |
RAN3 |
| R4-2218004 |
Reply LS on FS_VMR solutions review |
RAN3 |
| R4-2218005 |
Reply LS on enhanced cell reselection requirements |
RAN2 |
| R4-2218006 |
Reply LS on applicability of timing error margin of Rx TEG |
RAN2 |
| R4-2218007 |
Reply LS on clarification of RACH prioritisation rules between LTE and NR-U |
RAN2 |
| R4-2218008 |
LS on RACH-less handover in NTN |
RAN2 |
| R4-2218009 |
LS on the ue-PowerClassPerBandPerBC-r17(R4 16-8) |
RAN2 |
| R4-2218010 |
LS on FR2 UL gap |
RAN2 |
| R4-2218011 |
LS on RAN2 agreements about L1/L2-triggered mobility (LTM) |
RAN2 |
| R4-2218012 |
Reply LS on FS_VMR solutions review |
RAN2 |
| R4-2218013 |
Response to LS on extending the maximum range for NS values |
RAN2 |
| R4-2218014 |
Reply LS to RAN4 for further information on DMRS bundling |
RAN1 |
| R4-2218015 |
LS on updated Rel-17 RAN1 UE features lists for NR after RAN1#110bis-e |
RAN1 |
| R4-2218016 |
Reply LS on support of positioning in FR2-2 |
RAN1 |
| R4-2218017 |
Reply LS on Pemax,c of S-SSB transmission |
RAN1 |
| R4-2218018 |
Reply LS on TCI assumption for RSSI measurement for FR2-2 |
RAN1 |
| R4-2218019 |
LS on interference modelling for duplex evolution |
RAN1 |
| R4-2218020 |
LS on maximum number of UL subbands for duplex evolution |
RAN1 |
| R4-2218021 |
LS on work split principles adopted in RAN1 for power domain enhancements |
RAN1 |
| R4-2218022 |
Reply LS on active TCI state list for UL TCI |
RAN1 |
| R4-2218023 |
LS on UE capability and gNB configuration for UL Tx switching across 3 or 4 bands in Rel-18 |
RAN1 |
| R4-2218024 |
LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility |
RAN1 |
| R4-2218025 |
LS on enhancements to realize increasing UE power high limit for CA and DC |
RAN1 |
| 4.1 |
UE RF requirements for LTE and NR |
|
| R4-2218092 |
Addition of FR1 UL MIMO EVM measurement description |
Rohde & Schwarz |
| R4-2218093 |
Addition of FR1 UL MIMO EVM measurement description |
Rohde & Schwarz |
| R4-2218094 |
Addition of FR1 UL MIMO EVM measurement description |
Rohde & Schwarz |
| R4-2218095 |
Addition of FR2 UL MIMO EVM measurement description |
Rohde & Schwarz |
| R4-2218096 |
Addition of FR2 UL MIMO EVM measurement description |
Rohde & Schwarz |
| R4-2218097 |
Addition of FR2 UL MIMO EVM measurement description |
Rohde & Schwarz |
| R4-2218204 |
CR for TS 38.101-3 on clarifications for intra-band EN-DC configurations |
ZTE Corporation |
| R4-2218205 |
CR for TS 38.101-3 on clarifications for intra-band EN-DC configurations (Rel-16) |
ZTE Corporation |
| R4-2218206 |
CR for TS 38.101-3 on clarifications for intra-band EN-DC configurations (Rel-17) |
ZTE Corporation |
| R4-2218274 |
Addition of CA_n77-n78 to CA Band table R17 |
Nokia |
| R4-2218275 |
Addition of CA_n77-n78 to CA Band table R16 |
Nokia |
| R4-2218276 |
Correction to n91,n92,n93 and n94 co-ex R17 |
Nokia |
| R4-2218277 |
Correction to n91,n92,n93 and n94 co-ex R16 |
Nokia |
| R4-2218316 |
Annex G Clarifications on diagram related to measurement point for difference of relative phase/power error for UL coherent MIMO (Rel-15) |
Keysight technologies UK Ltd |
| R4-2218317 |
Annex G Clarifications on diagram related to measurement point for difference of relative phase/power error for UL coherent MIMO (Rel-16) |
Keysight technologies UK Ltd |
| R4-2218318 |
Annex G Clarifications on diagram related to measurement point for difference of relative phase/power error for UL coherent MIMO (Rel-17) |
Keysight technologies UK Ltd |
| R4-2218361 |
CR for TS 38.101-1 Rel-16: Correcting critical error with co-existence for band CA_n8-n40 |
Apple |
| R4-2218362 |
CR for TS 38.101-1 Rel-17 CAT-A: Correcting critical error with co-existence for band CA_n8-n40 |
Apple |
| R4-2218364 |
CR for TS 38.101-3 Rel-16: Corrections on band combinations for UE co-existence |
Apple |
| R4-2218365 |
CR for TS 38.101-3 Rel-17 CAT-A: Corrections on band combinations for UE co-existence |
Apple |
| R4-2218527 |
On the support of n41 NS_47 with PC1.5 |
SoftBank Corp. |
| R4-2218650 |
30MHz reconfiguration failure when accessing 40MHz network of n28 |
CMCC |
| R4-2218762 |
Rel16 Cat F Correction CR on adding the missing fallback combination DC_66A-66A_n66A |
Samsung |
| R4-2218772 |
Operation with Different Channel BWs in n28 |
Qualcomm Incorporated |
| R4-2218811 |
Clarification of carrier resource grid mapping |
Ericsson |
| R4-2218812 |
Clarification of carrier resource grid mapping |
Ericsson |
| R4-2218813 |
Clarification of carrier resource grid mapping |
Ericsson |
| R4-2218814 |
Carrier resource grid mapping to channel raster and use of UE-specific bandwidth |
Ericsson |
| R4-2218815 |
Carrier resource grid mapping to channel raster and use of UE-specific bandwidth |
Ericsson |
| R4-2218816 |
Carrier resource grid mapping to channel raster and use of UE-specific bandwidth |
Ericsson |
| R4-2218817 |
Carrier resource grid mapping to channel raster and use of UE-specific bandwidth |
Ericsson |
| R4-2218818 |
Carrier resource grid mapping to channel raster and use of UE-specific bandwidth |
Ericsson |
| R4-2218819 |
Carrier resource grid mapping to channel raster and use of UE-specific bandwidth |
Ericsson |
| R4-2218820 |
Draft LS to RAN2 on simultaneous Rx-Tx for band pairs of an advertised BC |
Ericsson |
| R4-2218881 |
Clarification for "dualUL" requirements for Time mask for Tx switching for SA (Rel-16) |
vivo |
| R4-2218882 |
Clarification for "dualUL" requirements for Time mask for Tx switching for SA (Rel-17) |
vivo |
| R4-2218883 |
Clarification for "dualUL" requirements for Time mask for Tx switching for NSA |
vivo |
| R4-2218884 |
Clarification for "dualUL" requirements for Time mask for Tx switching for NSA |
vivo |
| R4-2218914 |
CR to R16 TS38.101-1 maintenance for UE co-ex requirements for UL CA |
NTT DOCOMO, INC. |
| R4-2219130 |
CR for Rel-16 38.101-2 to correct the side condition for SSB and CSI-RS based |
Xiaomi |
| R4-2219131 |
CR for Rel-16 38.101-2 to correct the side condition for CSI-RS based |
Xiaomi |
| R4-2219132 |
CR for Rel-17 38.101-2 to correct the side condition for CSI-RS based |
Xiaomi |
| R4-2219194 |
CR to TS38.101-3[R15] 4Rx MSD for ENDC |
ZTE Corporation, CHTTL, Skyworks |
| R4-2219195 |
CR to TS38.101-3[R16] 4Rx MSD for ENDC |
ZTE Corporation, CHTTL, Skyworks |
| R4-2219196 |
CR to TS38.101-3[R17] 4Rx MSD for ENDC |
ZTE Corporation, CHTTL, Skyworks |
| R4-2219382 |
CR for an update on output power dynamics for intra-band EN-DC from Rel.16 |
CHTTL, MediaTek Inc., SGS Wireless |
| R4-2219383 |
CR for an update on output power dynamics for intra-band EN-DC from Rel.16 |
CHTTL, MediaTek Inc., SGS Wireless |
| R4-2219471 |
CR to 38.101-1 on removing ambiguity in CA MPR definition |
Qualcomm Inc. |
| R4-2219472 |
CR to 38.101-1 on removing ambiguity in CA MPR definition |
Qualcomm Inc. |
| R4-2219473 |
CR to 38.101-2 on removing ambiguity in CA MPR definition |
Qualcomm Inc. |
| R4-2219474 |
CR to 38.101-2 on removing ambiguity in CA MPR definition |
Qualcomm Inc. |
| R4-2219580 |
R15 CR on inter band ENDC OOBE correction |
OPPO |
| R4-2219581 |
R16 CR on inter band ENDC OOBE correction (CAT-A) |
OPPO |
| R4-2219582 |
R17 CR on inter band ENDC OOBE correction (CAT-A) |
OPPO |
| R4-2219688 |
CR on Pemax definition R16 |
Xiaomi |
| R4-2219689 |
CR on Pemax definition R17 |
Xiaomi |
| R4-2219690 |
on the Pemax for PSFCH |
Xiaomi |
| R4-2219776 |
EIRP-based test metric for FR2 SEM |
Anritsu Limited |
| R4-2219777 |
CR on ‘Annex G Difference of relative phase and power errors’ for FR1 UL coherent MIMO |
Anritsu Limited |
| R4-2219778 |
CR on ‘Annex G Difference of relative phase and power errors’ for FR1 UL coherent MIMO |
Anritsu Limited |
| R4-2219779 |
CR on ‘Annex G Difference of relative phase and power errors’ for FR1 UL coherent MIMO |
Anritsu Limited |
| R4-2219780 |
CR on TDD RMC for Intra-band EN-DC - TS 38.101-1 |
Anritsu Limited |
| R4-2219781 |
CR on TDD RMC for Intra-band EN-DC - TS 38.101-1 |
Anritsu Limited |
| R4-2219782 |
CR on TDD RMC for Intra-band EN-DC - TS 38.101-1 |
Anritsu Limited |
| R4-2219783 |
CR on TDD RMC for Intra-band EN-DC - TS 38.101-3 |
Anritsu Limited |
| R4-2219784 |
CR on TDD RMC for Intra-band EN-DC - TS 38.101-3 |
Anritsu Limited |
| R4-2219785 |
CR on TDD RMC for Intra-band EN-DC - TS 38.101-3 |
Anritsu Limited |
| R4-2219811 |
Correction to DL RMC (Rel-15) |
Huawei, HiSilicon |
| R4-2219812 |
Correction to DL RMC (Rel-16) |
Huawei, HiSilicon |
| R4-2219813 |
Correction to DL RMC (Rel-17) |
Huawei, HiSilicon |
| R4-2219820 |
EIRP-based test metric for FR2 SEM verifications |
Apple |
| R4-2220458 |
Way forward on operation with different channel BWs for n28 |
CMCC |
| R4-2220519 |
Ad hoc minutes for R16/R15 UE RF maintenance |
OPPO |
| R4-2220520 |
Draft LS to RAN2 on simultaneous Rx-Tx for band pairs of an advertised BC |
Ericsson |
| R4-2220521 |
LS on FR2 SEM test time reduction |
Apple |
| R4-2220522 |
Addition of CA_n77-n78 to CA Band table R16 |
Nokia |
| R4-2220523 |
Correction to n91,n92,n93 and n94 co-ex R16 |
Nokia |
| R4-2220524 |
CR for TS 38.101-3 on clarifications for intra-band EN-DC configurations |
ZTE Corporation |
| R4-2220531 |
Addition of CA_n77-n78 to CA Band table R17 |
Nokia |
| R4-2220532 |
Addition of CA_n77-n78 to CA Band table R16 |
Nokia |
| R4-2220570 |
CR to 38.101-1 on removing ambiguity in CA MPR definition |
Qualcomm Inc. |
| R4-2220600 |
LS on FR2 SEM test time reduction |
Apple |
| R4-2220816 |
Way forward on operation with different channel BWs for n28 |
CMCC |
| R4-2220817 |
CR to 38.101-1 on removing ambiguity in CA MPR definition |
Qualcomm Inc. |
| R4-2220822 |
Rel16 Cat F Correction CR on adding the missing fallback combination DC_66A-66A_n66A |
Samsung |
| R4-2220858 |
CR on TDD RMC for Intra-band EN-DC - TS 38.101-1 |
Anritsu Limited |
| R4-2220859 |
CR on TDD RMC for Intra-band EN-DC - TS 38.101-3 |
Anritsu Limited |
| 4.2 |
BS RF requirements and conformance test for LTE and NR |
|
| R4-2218469 |
CR for TS 38.141-1, Correct Mapping of PRBs to n_RNTI for NR-FR1-TM in clause 4.9.2.3.2 |
CATT |
| R4-2218506 |
CR to 37.141 - TC22 generation misalignment when supporting multiple NB-IoT standalone carriers |
Ericsson |
| R4-2218507 |
CR to 37.141 - TC22 generation misalignment when supporting multiple NB-IoT standalone carriers |
Ericsson |
| R4-2218508 |
CR to 37.141 - TC22 generation misalignment when supporting multiple NB-IoT standalone carriers |
Ericsson |
| R4-2218903 |
CR to 38.104: Spurious emission requirements, Rel-16 |
NEC |
| R4-2218905 |
CR to 38.141-1: Spurious emission requirements, Rel-16 |
NEC |
| R4-2219158 |
CR to 38.141-1: Additional BS conformance to other standards |
Huawei, HiSilicon |
| R4-2219159 |
CR to 38.141-1: Additional BS conformance to other standards |
Huawei, HiSilicon |
| R4-2219160 |
CR to 38.141-1: Additional BS conformance to other standards |
Huawei, HiSilicon |
| R4-2219161 |
CR to 38.141-2: Additional BS conformance to other standards |
Huawei, HiSilicon |
| R4-2219162 |
CR to 38.141-2: Additional BS conformance to other standards |
Huawei, HiSilicon |
| R4-2219163 |
CR to 38.141-2: Additional BS conformance to other standards |
Huawei, HiSilicon |
| R4-2219964 |
CR to TS 36.141: FFS/TBD removal for band 23 co-ex for HomeNB, TT derivation, and multi-band requirements, Rel-15 |
Huawei, HiSilicon |
| R4-2219965 |
CR to TS 36.141: FFS/TBD removal for band 23 co-ex for HomeNB, TT derivation, and multi-band requirements, Rel-16 |
Huawei, HiSilicon |
| R4-2219966 |
CR to TS 36.141: FFS/TBD removal for band 23 co-ex for HomeNB, TT derivation, and multi-band requirements, Rel-17 |
Huawei, HiSilicon |
| R4-2220256 |
CR to 38.104: Spurious emission requirements, Rel-16 |
NEC |
| R4-2220258 |
CR to 38.141-1: Spurious emission requirements, Rel-16 |
NEC |
| R4-2220865 |
CR to 38.141-1: Spurious emission requirements, Rel-16 |
NEC |
| 4.4 |
RRM requirements for LTE and NR |
|
| R4-2218081 |
CR to TS 38.133: Corrections to NR RRM test cases (Rel 15) |
Rohde & Schwarz |
| R4-2218082 |
CR to TS 38.133: Corrections to NR RRM test cases (Rel 16) |
Rohde & Schwarz |
| R4-2218083 |
CR to TS 38.133: Corrections to NR RRM test cases (Rel 17) |
Rohde & Schwarz |
| R4-2218084 |
CR to TS 38.133: Corrections to NR positioning and high speed train test cases (Rel 16) |
Rohde & Schwarz |
| R4-2218085 |
CR to TS 38.133: Corrections to NR positioning and high speed train test cases (Rel 17) |
Rohde & Schwarz |
| R4-2218132 |
CR on NR RRM maintenance R15 |
Apple |
| R4-2218133 |
CR on NR RRM maintenance R16 |
Apple |
| R4-2218134 |
CR on NR RRM maintenance R17 |
Apple |
| R4-2218173 |
Editorial CR on scheduling restrictions for L3 measurements in FR2 (Rel-16) |
Apple |
| R4-2218174 |
Editorial CR on scheduling restrictions for L3 measurements in FR2 (Rel-17) |
Apple |
| R4-2218210 |
CR to CSI-RS, RLM and BWP switching in annex |
Anritsu Corporation |
| R4-2218211 |
CR to CSI-RS, RLM and BWP switching in annex |
Anritsu Corporation |
| R4-2218212 |
CR to CSI-RS, RLM and BWP switching in annex |
Anritsu Corporation |
| R4-2218353 |
Update on Scell activation and deactivation and Control Channel RMC for RLM FR2 (Rel-15) |
Keysight Technologies UK Ltd |
| R4-2218354 |
Update on Scell activation and deactivation and Control Channel RMC for RLM FR2 (Rel-16) |
Keysight Technologies UK Ltd |
| R4-2218355 |
Update on Scell activation and deactivation and Control Channel RMC for RLM FR2 (Rel-17) |
Keysight Technologies UK Ltd |
| R4-2218356 |
Update to L1-RSRP test scenarios (Rel-15) |
Keysight Technologies UK Ltd |
| R4-2218357 |
Update to L1-RSRP test scenarios (Rel-16) |
Keysight Technologies UK Ltd |
| R4-2218358 |
Update to L1-RSRP test scenarios (Rel-17) |
Keysight Technologies UK Ltd |
| R4-2218422 |
Modification on TS38.133 for Rel-16 |
CATT |
| R4-2218423 |
Modification on TS38.133 for Rel-16 |
CATT |
| R4-2218453 |
CR on positioning measurement accuracy requirements in R16 |
CATT |
| R4-2218454 |
CR on positioning measurement accuracy requirements in R16 |
CATT |
| R4-2218533 |
R15 Cat-F CR testcase correction from R15 TS 38.133 |
Qualcomm Incorporated |
| R4-2218534 |
R16 Cat-A CR testcase correction from R15 TS 38.133 |
Qualcomm Incorporated |
| R4-2218535 |
R17 Cat-A CR testcase correction from R15 TS 38.133 |
Qualcomm Incorporated |
| R4-2218536 |
R16 Cat-F CR testcase correction from R16 TS 38.133 |
Qualcomm Incorporated |
| R4-2218537 |
R17 Cat-A CR testcase correction from R16 TS 38.133 |
Qualcomm Incorporated |
| R4-2218653 |
CR on test case correction for timing advance |
CMCC |
| R4-2218654 |
CR on test case correction for timing advance |
CMCC |
| R4-2218655 |
CR on test case correction for timing advance |
CMCC |
| R4-2218675 |
38133 CR on SRS configuration for SRS carrier based switching |
Nokia, Nokia Shanghai Bell, Qualcomm, Inc |
| R4-2218676 |
38133 Cat. A CR on SRS configuration for SRS carrier based switching |
Nokia, Nokia Shanghai Bell, Qualcomm, Inc |
| R4-2218746 |
CR on TC for known PSCell addition in R15 |
MediaTek Inc. |
| R4-2218747 |
CR on TC for known PSCell addition in R16 |
MediaTek Inc. |
| R4-2218748 |
CR on TC for known PSCell addition in R17 |
MediaTek Inc. |
| R4-2218749 |
CR on TC for inter-RAT NR Cell reselection in R15 |
MediaTek Inc. |
| R4-2218750 |
CR on TC for inter-RAT NR Cell reselection in R16 |
MediaTek Inc. |
| R4-2218751 |
CR on TC for inter-RAT NR Cell reselection in R17 |
MediaTek Inc. |
| R4-2218790 |
CR to TS 38.133 Correction to conditional handover requirements(Rel-16) |
vivo |
| R4-2218791 |
CR to TS 38.133 Correction to conditional handover requirements(Rel-17) |
vivo |
| R4-2218792 |
CR to TS 38.133 Correction to conditional PSCell change requirements(Rel-16) |
vivo |
| R4-2218793 |
CR to TS 38.133 Correction to conditional PSCell change requirements(Rel-17) |
vivo |
| R4-2219168 |
Correction of L1 L3 measurenent sharing factors for inter-frequency L3 measurement performed outside gaps in R16 |
vivo |
| R4-2219169 |
Correction of L1 L3 measurenent measurement sharing factors for inter-frequency L3 measurement performed outside gaps in R17 |
vivo |
| R4-2219405 |
Correction on Aperiodic CSI-RS RMCs and RLM in-sync test cases for R15 |
Huawei, HiSilicon |
| R4-2219406 |
Correction on Aperiodic CSI-RS RMCs and RLM in-sync test cases for R16 |
Huawei, HiSilicon |
| R4-2219407 |
Correction on Aperiodic CSI-RS RMCs and RLM in-sync test cases for R17 |
Huawei, HiSilicon |
| R4-2219527 |
Discussion on remaining issues in R16 POS |
Huawei, HiSilicon |
| R4-2219528 |
CR on positioning requirements R16 |
Huawei, HiSilicon |
| R4-2219529 |
CR on positioning requirements R17 |
Huawei, HiSilicon |
| R4-2219847 |
Correction to Idle Mode CA/DC Measurement Tests in TS 38.133 |
Ericsson |
| R4-2219848 |
Correction to Idle Mode CA/DC Measurement Tests in TS 38.133 |
Ericsson |
| R4-2219909 |
PRS measurement requirements for Deferred MT-LR Periodic Location |
Nokia, Nokia Shanghai Bell |
| R4-2219910 |
CR 38.133 on PRS measurement period for Deferred MT-LR |
Nokia, Nokia Shanghai Bell |
| R4-2219911 |
CR 38.133 on PRS measurement period for Deferred MT-LR |
Nokia, Nokia Shanghai Bell |
| R4-2219937 |
CR on Rel-16 measurements and UE specific CBW switch maintenance |
Ericsson |
| R4-2219938 |
CR on Rel-17 measurements and UE specific CBW switch maintenance |
Ericsson |
| R4-2220371 |
CR to CSI-RS, RLM and BWP switching in annex |
Anritsu Corporation |
| R4-2220372 |
CR to CSI-RS, RLM and BWP switching in annex |
Anritsu Corporation |
| R4-2220373 |
Update to L1-RSRP test scenarios (Rel-15) |
Keysight Technologies UK Ltd |
| R4-2220374 |
Editorial CR on scheduling restrictions for L3 measurements in FR2 (Rel-16) |
Apple |
| R4-2220375 |
Update on Scell activation and deactivation and Control Channel RMC for RLM FR2 (Rel-15) |
Keysight Technologies UK Ltd |
| R4-2220376 |
R15 Cat-F CR testcase correction from R15 TS 38.133 |
Qualcomm Incorporated |
| R4-2220377 |
CR on TC for known PSCell addition in R15 |
MediaTek Inc. |
| R4-2220378 |
Correction on Aperiodic CSI-RS RMCs and RLM in-sync test cases for R15 |
Huawei, HiSilicon |
| R4-2220379 |
Correction on Aperiodic CSI-RS RMCs and RLM in-sync test cases for R16 |
Huawei, HiSilicon |
| R4-2220380 |
R16 Cat-F CR testcase correction from R16 TS 38.133 |
Qualcomm Incorporated |
| R4-2220381 |
CR on positioning requirements R16 |
Huawei, HiSilicon |
| R4-2220382 |
Correction of L1 L3 measurenent measurement sharing factors for inter-frequency L3 measurement performed outside gaps in R16 |
vivo |
| R4-2220383 |
Correction to Idle Mode CA/DC Measurement Tests in TS 38.133 |
Ericsson |
| R4-2220384 |
CR to TS 38.133: Corrections to NR positioning and high speed train test cases (Rel 16) |
Rohde & Schwarz |
| R4-2220429 |
CR 38.133 on PRS measurement period for Deferred MT-LR |
Nokia, Nokia Shanghai Bell |
| R4-2220435 |
CR on Rel-16 measurements and UE specific CBW switch maintenance |
Ericsson |
| R4-2220726 |
Modification on TS38.133 for Rel-16 |
CATT |
| R4-2220727 |
Correction to Idle Mode CA/DC Measurement Tests in TS 38.133 |
Ericsson |
| R4-2220739 |
Correction on Aperiodic CSI-RS RMCs and RLM in-sync test cases for R15 |
Huawei, HiSilicon |
| R4-2220740 |
Correction on Aperiodic CSI-RS RMCs and RLM in-sync test cases for R16 |
Huawei, HiSilicon |
| 4.5 |
Demodulation and CSI requirements for LTE and NR |
|
| R4-2218052 |
Draft CR on clarification of PDSCH and PDSCH DMRS precoder configuration |
Qualcomm Incorporated |
| R4-2218053 |
Draft CR on clarification of PDSCH and PDSCH DMRS precoder configuration |
Qualcomm Incorporated |
| R4-2218087 |
Correction to UL scheduling for TDD CSI TCs |
Rohde & Schwarz |
| R4-2218088 |
Correction to UL scheduling for TDD CSI TCs |
Rohde & Schwarz |
| R4-2218089 |
Correction to UL scheduling for TDD CSI TCs |
Rohde & Schwarz |
| R4-2218090 |
Correction to LTE-NR coexistence requirements |
Rohde & Schwarz |
| R4-2218091 |
Correction to LTE-NR coexistence requirements |
Rohde & Schwarz |
| R4-2218213 |
CR to dl-DataToUL-ACK for PDSCH demod CA TCs |
Anritsu Corporation |
| R4-2218214 |
CR to dl-DataToUL-ACK for PDSCH demod CA TCs |
Anritsu Corporation |
| R4-2218244 |
CR to TS38.101-4, Corrections to NR-U (Rel-16) |
MediaTek inc. |
| R4-2218245 |
CR to TS38.101-4, Corrections to NR-U (Rel-17) |
MediaTek inc. |
| R4-2218722 |
CR for TS38.104 correction on normal PUSCH requirements (Rel-16) |
Ericsson |
| R4-2219522 |
CR on corrections to parameters of Rel-16 V2X HARQ buffer test in TS 38.101-4 |
Huawei, HiSilicon |
| R4-2219523 |
CR on corrections to parameters of Rel-17 V2X HARQ buffer test in TS 38.101-4 |
Huawei, HiSilicon |
| R4-2219524 |
CR on corrections to parameters of Rel-16 NR-U test in TS 38.101-4 |
Huawei, HiSilicon |
| R4-2219525 |
CR on corrections to parameters of Rel-17 NR-U test in TS 38.101-4 |
Huawei, HiSilicon |
| R4-2219961 |
CR for 38.101-4 on correction of FR2 PBCH Test Parameters |
Nokia, Nokia Shanghai Bell |
| R4-2219962 |
CR for 38.101-4 on correction of FR2 PBCH Test Parameters |
Nokia, Nokia Shanghai Bell |
| R4-2219963 |
CR for 38.101-4 on correction of FR2 PBCH Test Parameters |
Nokia, Nokia Shanghai Bell |
| R4-2220864 |
CR on corrections to parameters of Rel-16 NR-U test in TS 38.101-4 |
Huawei, HiSilicon |
| 4.7 |
Moderator summary and conclusions |
|
| R4-2220047 |
Topic summary for [105][201] R15_maintenance_RRM |
Moderator (Huawei) |
| R4-2220048 |
Topic summary for [105][202] R16_maintenance_RRM |
Moderator (Apple) |
| R4-2220081 |
Topic summary for [105][101] Upto_R16_UERF_maintenance |
Moderator (OPPO) |
| 5.1 |
BS RF requirements and conformance test |
|
| R4-2218098 |
Justification for corrections for 100MHz CBW inclusion for n46, n96 and n102 in 38.104 |
CableLabs, Charter Communications, Nokia |
| R4-2218124 |
Corrections for 100MHz CBW inclusion for n46 n96 and n102 |
CableLabs, Charter Communications, Nokia |
| R4-2218904 |
CR to 38.104: Spurious emission requirements, Rel-17 |
NEC |
| R4-2218906 |
CR to 38.141-1: Spurious emission requirements, Rel-17 |
NEC |
| R4-2218907 |
CR to 38.141-2: Spurious emission requirements, Rel-17 |
NEC |
| R4-2219798 |
CR on case-6 timing for eIAB_RF |
Ericsson |
| R4-2219799 |
IAB case6 timing |
Ericsson |
| R4-2219800 |
CR on eIAB performance -general requirement -38.176-1 |
Ericsson |
| R4-2219801 |
CR on eIAB performance -general requirement -38.176-2 |
Ericsson |
| R4-2219804 |
CR to TS 38.174 with bracket removal for timing error between IAB-DU and IAB-MT |
Nokia, Nokia Shanghai Bell |
| R4-2219865 |
CR to 37.104 on introduction of additional interfering signal |
Nokia, Nokia Shanghai Bell |
| R4-2219866 |
CR to 37.141 on introduction of additional interfering signal |
Nokia, Nokia Shanghai Bell |
| R4-2220257 |
CR to 38.104: Spurious emission requirements, Rel-17 |
NEC |
| R4-2220259 |
CR to 38.141-1: Spurious emission requirements, Rel-17 |
NEC |
| R4-2220260 |
CR to 38.141-2: Spurious emission requirements, Rel-17 |
NEC |
| R4-2220262 |
Corrections for 100MHz CBW inclusion for n46 n96 and n102 |
CableLabs, Charter Communications, Nokia |
| R4-2220608 |
CR on case-6 timing for eIAB_RF |
Ericsson, Nokia |
| R4-2220866 |
CR to 38.104: Spurious emission requirements, Rel-17 |
NEC |
| 5.2 |
UE RF requirements |
|
| R4-2218029 |
CR for TS 38.101-1, Correction of maximum configured power for PSFCH in Rel-17 sidelink enhancement |
LG Electronics Deutschland |
| R4-2218038 |
CR for 38.101-3 to Add Missing MSD Items for PC2 EN-DC combos |
AT&T, Verizon |
| R4-2218123 |
ACS and IBB in-gap exemption for CA_n258-n261 |
Apple |
| R4-2218191 |
Modification on power imbalance requirement for EN-DC with overlapping DL frequency |
Apple |
| R4-2218218 |
CR to TS38.101-2 PC3 TIB values for FR2 inter-band UL CA |
NTT DOCOMO, INC. |
| R4-2218263 |
CR correction to n100 and n101 UE to UE coexsistence tables and revoval of brackets |
Nokia |
| R4-2218264 |
CR addition of protection for n100 and n101 into 36.101 |
Nokia |
| R4-2218265 |
CR addition of protection for n100 and n101 into 38.101-3 |
Nokia |
| R4-2218266 |
CR addition of protection for n100 and n101 into 38.101-5 |
Nokia |
| R4-2218273 |
LTE CA corrections |
Nokia |
| R4-2218296 |
Final FCC regulation decision on NR V2X service |
Facebook Japan K.K. |
| R4-2218305 |
Definition of Window lengths for 35 and 45 MHz channel bandwidths |
Keysight technologies UK Ltd |
| R4-2218363 |
CR for TS 38.101-1 Rel-17: Corrections on band combinations for UE co-existence |
Apple |
| R4-2218366 |
CR for TS 38.101-3 Rel-17: Corrections on band combinations for UE co-existence |
Apple |
| R4-2218375 |
CR for updating the note of mandatory simultaneous Rx/Tx capability for FR1 NR-CA combinations |
KDDI Corporation |
| R4-2218532 |
CR on NR-U A-MPR for PC5 VLP |
LG Electronics |
| R4-2218763 |
Rel17 Cat F Correction CR on adding missing BCS for DC_66A-66A_n66A |
Samsung |
| R4-2218766 |
Rel17 Cat F CR Correct the DL configuration for harmonic MSD for CA_n12-n66 and CA_n25-n71 |
Samsung |
| R4-2218821 |
FR2 SEM test time reduction by utilizing coarse TRP grid |
Ericsson |
| R4-2218822 |
Correction to UE power classes for CA configurations for HPUE |
Ericsson |
| R4-2218823 |
Removal of the CA bandwidth classes R-U |
Ericsson |
| R4-2218868 |
CR on ACS/IBB of FR2 inter-band CA |
vivo |
| R4-2218889 |
Discussion on maximum configured power of PSFCH in Rel-17 sidelink enhancement |
LG Electronics Deutschland |
| R4-2218913 |
CR to R17 TS38.101-1 maintenance for UE co-ex requirements for UL CA |
NTT DOCOMO, INC. |
| R4-2218953 |
Rel-17 CR 38.101-3 for two and three band CA corrections |
Ericsson |
| R4-2219197 |
Correction on the HigherPowerLimitCADC and powerClassPerBand IE |
ZTE Corporation |
| R4-2219337 |
CR for corrections on Rel-17 band combinations in TS36.101 |
Google Inc. |
| R4-2219387 |
CR on R17 TS38.101-1 Add HPUE configurations for intra-band CA supported in R16 spec |
Huawei,HiSilicon |
| R4-2219423 |
CR for corrections on Rel-17 band combinations in TS38.101-1 |
Google Inc. |
| R4-2219425 |
CR for corrections on Rel-17 band combinations in TS38.101-3 |
Google Inc. |
| R4-2219692 |
CR TS38.101-1 R17 Re-construct NR-U clause structure and introduce missing requirements |
Skyworks Solutions Inc., ZTE Corporation |
| R4-2219693 |
Corrections for NR-U TS structure and missing requirements |
Skyworks Solutions Inc., ZTE Corporation. |
| R4-2219698 |
CR TS38.101-1 R17 Corrections to Cross-band isolation and Rx harmonic mixing MSD |
Skyworks Solutions Inc., ZTE Corporation |
| R4-2219721 |
DraftCR for 38.101-1: Add missing PC2 CA_n77C in uplink configurations |
Verizon Denmark |
| R4-2219749 |
Maximum aggregated channel bandwidth for FR1 CA |
Verizon, Qualcomm |
| R4-2219754 |
CR on TS 38.101-3 to correct delta TIB table for NE-DC and EN-DC combinations |
ZTE Corporation |
| R4-2219907 |
Multi-PSFCH transmission from multiple resource pools |
Qualcomm Technologies Int |
| R4-2219982 |
Enabling PC2 FDD for PC2 UL CA |
Qualcomm Incorporated |
| R4-2219983 |
Enabling PC2 FDD for PC2 DC |
Qualcomm Incorporated |
| R4-2219994 |
CR for 38.101-1: Corrections for 5 MHz for n41 and other errors |
T-Mobile USA |
| R4-2219995 |
CR for 38.101-1: NR CA table corrections |
T-Mobile USA, Nokia |
| R4-2220464 |
DraftCR for 38.101-1: Add missing PC2 CA_n77C in uplink configurations |
Verizon Denmark, T-Mobile |
| R4-2220527 |
CR TS38.101-1 R17 Re-construct NR-U clause structure and introduce missing requirements |
Skyworks Solutions Inc., ZTE Corporation |
| R4-2220528 |
CR TS38.101-1 R17 Corrections to Cross-band isolation and Rx harmonic mixing MSD |
Skyworks Solutions Inc., ZTE Corporation |
| R4-2220549 |
LTE CA corrections |
Nokia |
| R4-2220553 |
LS on PSFCH configured power with multiple resource pools |
LG Electronics |
| R4-2220578 |
CR to TS38.101-2 PC3 TIB values for FR2 inter-band UL CA |
NTT DOCOMO, INC. |
| R4-2220591 |
CR for corrections on Rel-17 band combinations in TS36.101 |
Google Inc. |
| R4-2220592 |
CR for corrections on Rel-17 band combinations in TS38.101-1 |
Google Inc. |
| R4-2220594 |
CR for corrections on Rel-17 band combinations in TS38.101-3 |
Google Inc. |
| R4-2220595 |
CR to TS38.101-2 PC3 TIB values for FR2 inter-band UL CA |
NTT DOCOMO, INC. |
| R4-2220596 |
CR for TS 38.101-1 Rel-17: Corrections on band combinations for UE co-existence |
Apple |
| R4-2220597 |
Correction to UE power classes for CA configurations for HPUE |
Ericsson |
| R4-2220598 |
CR for updating the note of mandatory simultaneous Rx/Tx capability for FR1 NR-CA combinations |
KDDI Corporation |
| R4-2220823 |
Rel17 Cat F Correction CR on adding missing BCS for DC_66A-66A_n66A |
Samsung |
| 5.3 |
RRM requirements |
|
| R4-2218135 |
On PUCCH SCell activation requirement |
Apple |
| R4-2218145 |
CR on NCSG test case |
Apple |
| R4-2218146 |
CR on R17 HST test case - SA event triggered reporting tests without gap under DRX for UE configured with highSpeedMeasCA-Scell-r17 |
Apple |
| R4-2218289 |
CR on release independent for FR1 HST RRM |
CMCC |
| R4-2218290 |
CR on release independent for FR1 HST RRM |
CMCC |
| R4-2218374 |
R17 maintenance discussion |
Qualcomm Israel Ltd. |
| R4-2218389 |
CR on Tidentify_inter_without_index when deriveSSB-IndexFromCellInter is configured |
CMCC |
| R4-2218390 |
Discussion on network flag deriveSSB-IndexFromCellInter |
CMCC |
| R4-2218424 |
Discussion on remaining issues for PUCCH Scell activation |
CATT |
| R4-2218425 |
Completing PUCCH SCell activation requirement |
CATT |
| R4-2218440 |
CR on R17 positioning measurement accuracy requirements |
CATT |
| R4-2218656 |
Discussion on test cases for RLM/BFD measurement relaxation |
CMCC |
| R4-2218657 |
CR on FR2 PSCell SSB-based BFD and CBD test for UE fulfilling relaxed measurement criterion |
CMCC |
| R4-2218677 |
38133CR on PUCCH SCell activation delay requirement |
Nokia, Nokia Shanghai Bell |
| R4-2218733 |
Discussion on R17 MR-DC enhancement |
MediaTek inc. |
| R4-2218734 |
CR for R17 MR-DC Enh on 38.133 |
MediaTek inc. |
| R4-2218735 |
CR on TC for R17 HST CA enhancement on deactivated SCell (EN-DC) in FR1 |
MediaTek inc. |
| R4-2218789 |
Remain issues on Efficient activation de-activation mechanism for one SCG |
vivo |
| R4-2218794 |
CR to TS 38.133 Correction to conditional PSCell addition requirements(Rel-17) |
vivo |
| R4-2218795 |
CR on RLM/BFD requirement for deactivated PSCell and SCG Activation Delay requirement |
vivo |
| R4-2219170 |
L1-SINR measurement accuracy requirements in R17 FR1 HST |
vivo |
| R4-2219171 |
Correction on SRS configurations for SRS antenna switching test cases |
vivo |
| R4-2219287 |
Discussion on L1-SINR and SS-SINR measurements for FR2 HST |
Samsung |
| R4-2219324 |
Discussion on Rel-17 remaining issues |
Ericsson |
| R4-2219325 |
CR on ConMGs |
Ericsson |
| R4-2219326 |
CR on cell reselection in Idle mode |
Ericsson |
| R4-2219327 |
CR on cell reselection in Idle mode for NR-U |
Ericsson |
| R4-2219455 |
Corrections to Rel.17 positioning test cases |
Ericsson |
| R4-2219456 |
Correction to PRS measurement period requirement in RRC_CONNECTED state |
Ericsson |
| R4-2219457 |
Correction to PRS measurement period requirement in RRC_INACTIVE state |
Ericsson |
| R4-2219458 |
Correction to RSTD measurement accuracy requirement for TEG based reporting |
Ericsson |
| R4-2219530 |
Discussion on remaining issues for Rel-17 positioning |
Huawei, HiSilicon |
| R4-2219531 |
CR on core requirements for Rel-17 positioning |
Huawei, HiSilicon |
| R4-2219532 |
CR on performance requirements for Rel-17 positioning |
Huawei, HiSilicon |
| R4-2219533 |
Further simulation results for PRS accuracy |
Huawei, HiSilicon |
| R4-2219711 |
CR to 38.133 on Rel-17 HST FR2 RRM Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2219712 |
On Remaining Open Issues in Rel-17 HST FR2 RRM Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2219750 |
CR - Corrections to core requirements for NR positioning |
Qualcomm Incorporated |
| R4-2219751 |
Pre-MG test case No 1-1 |
Intel Corporation, MediaTek, OPPO |
| R4-2219752 |
Discussion on performance requirements for PRS Measurement with reduced number of samples |
Intel Corporation |
| R4-2219753 |
Performance requirements for PRS Measurement with reduced number of samples |
Intel Corporation |
| R4-2219767 |
Draft CR to TS 38.133: Remedy the incorrect implementation in the section 4.2.2.4 |
Spreadtrum Communications |
| R4-2219888 |
NCSG nogap-noncsg inter-RAT LTE measurement requirement |
Qualcomm Israel Ltd. |
| R4-2219939 |
Maintenance CR on SCell activation/deactivation with PUCCH |
Ericsson |
| R4-2219940 |
Maintenance CR on HO with PSCell where PSCell is on CCA |
Ericsson |
| R4-2219941 |
Maintenance CR on HO with PSCell where PSCell is on CCA |
Ericsson |
| R4-2219942 |
Maintenance CR on UL gaps for Tx power management |
Ericsson |
| R4-2220346 |
CR on release independent for Rel-17 FR1 HST RRM |
CMCC |
| R4-2220347 |
CR on release independent for Rel-17 FR1 HST RRM |
CMCC |
| R4-2220348 |
WF on HST FR2 RRM maintenance |
Nokia |
| R4-2220349 |
Maintenance CR on SCell activation/deactivation with PUCCH |
Ericsson, Nokia, Huawei |
| R4-2220350 |
CR on R17 HST test case - SA event triggered reporting tests without gap under DRX for UE configured with highSpeedMeasCA-Scell-r17 |
Apple |
| R4-2220351 |
L1-SINR and SS-SINR measurement accuracy requirements in R17 FR1 HST |
vivo |
| R4-2220352 |
CR on R17 positioning measurement accuracy requirements |
CATT |
| R4-2220353 |
Performance requirements for PRS Measurement with reduced number of samples |
Intel Corporation |
| R4-2220354 |
CR on RLM/BFD requirement for deactivated PSCell and SCG Activation Delay requirement |
vivo |
| R4-2220355 |
CR to 38.133 on Rel-17 HST FR2 RRM Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2220356 |
WF on network flag deriveSSB-IndexFromCellInter |
CMCC |
| R4-2220357 |
CR on cell reselection in Idle mode |
Ericsson, NTT DOCOMO, Qualcomm Incorporated |
| R4-2220358 |
CR to TS 38.133: Remedy the incorrect implementation in the section 4.2.2.4 |
Spreadtrum Communications |
| R4-2220386 |
Maintenance CR on HO with PSCell where PSCell is on CCA |
Ericsson |
| R4-2220389 |
Corrections to Rel.17 positioning test cases |
Ericsson |
| R4-2220430 |
CR - Corrections to core requirements for NR positioning |
Qualcomm Incorporated |
| R4-2220441 |
CR on NCSG test case |
Apple |
| R4-2220452 |
WF on HST FR2 RRM maintenance |
Nokia |
| R4-2220453 |
CR to 38.133 on Rel-17 HST FR2 RRM Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2220454 |
CR on core requirements for Rel-17 positioning |
Huawei, HiSilicon |
| R4-2220455 |
CR on performance requirements for Rel-17 positioning |
Huawei, HiSilicon |
| R4-2220707 |
CR for R17 MR-DC Enh on 38.133 |
MediaTek inc. |
| R4-2220718 |
Performance requirements for PRS Measurement with reduced number of samples |
Intel Corporation |
| R4-2220719 |
CR for R17 MR-DC Enh on 38.133 |
MediaTek inc. |
| R4-2220720 |
CR to TS 38.133 Correction to conditional PSCell addition requirements(Rel-17) |
vivo |
| R4-2220721 |
WF on HST FR2 RRM maintenance |
Nokia |
| R4-2220722 |
WF on network flag deriveSSB-IndexFromCellInter |
CMCC |
| R4-2220723 |
LS on UE capability for network flag deriveSSB-IndexFromCellInter |
CMCC |
| R4-2220724 |
CR on Tidentify_inter_without_index when deriveSSB-IndexFromCellInter is configured |
CMCC |
| R4-2220725 |
CR on cell reselection in Idle mode |
Ericsson, NTT DOCOMO, Qualcomm Incorporated |
| R4-2220738 |
CR on TC for R17 HST CA enhancement on deactivated SCell (EN-DC) in FR1 |
MediaTek inc. |
| 5.4 |
Demodulation and CSI requirements |
|
| R4-2218054 |
Draft CR on clarification of PDSCH and PDSCH DMRS precoder configuration |
Qualcomm Incorporated |
| R4-2218059 |
Maintenance on the CRS-IM test requirements under non-DSS scenarios |
China Telecom |
| R4-2218060 |
CR on maintenance of PDSCH CRS-IM demod requirements |
China Telecom |
| R4-2218061 |
CR on maintenance on PDSCH 4Rx demod requirements for MU-MIMO IRC |
China Telecom |
| R4-2218175 |
Simulation results for PDSCH demod requirements in ICI |
Apple |
| R4-2218176 |
Summary of simulation results for inter cell interference MMSE-IRC receiver requirements |
Apple |
| R4-2218177 |
CR for Maintenance of PDSCH demod requirements with inter-cell interference |
Apple |
| R4-2218291 |
CR on release independent for FR1 HST demodulation |
CMCC |
| R4-2218658 |
CR on TDD PDSCH CRS-IM demod requirements for Scenario2 and PDSCH MMSE-IRC demod requirements with ICI |
CMCC, China Telecom |
| R4-2218723 |
CR for TS38.104 correction on normal PUSCH requirements (Rel-17) |
Ericsson |
| R4-2219023 |
CR on NPUSCH format1 demodulation requirement for TS 36.104 |
Samsung |
| R4-2219279 |
CR to 38.101-4: PDSCH requirement for CRS-IM TDD |
Ericsson |
| R4-2219280 |
CR to 38.101-4: Correction on the testability for CRS-IM requirements |
Ericsson |
| R4-2219518 |
CR on cleanup for Rel-17 NPDSCH requirements with 16QAM in TS 36.101 |
Huawei, HiSilicon |
| R4-2219519 |
CR on cleanup for Rel-17 NPUSCH format 1 requirements with 16QAM in TS 36.104 |
Huawei, HiSilicon |
| R4-2219520 |
CR on cleanup for Rel-17 NPUSCH format 1 requirements with 16QAM in TS 36.141 |
Huawei, HiSilicon |
| R4-2219521 |
CR on modification on Rel-17 CRS-IM performance requirements in TS 38.101-4 |
Huawei, HiSilicon |
| R4-2219991 |
CR 36.141 on Finalization of NPUSCH format 1 16QAM test requirement |
Nokia, Nokia Shanghai Bell |
| R4-2220198 |
CR on maintenance of PDSCH CRS-IM demod requirements |
China Telecom |
| R4-2220199 |
CR on modification on Rel-17 CRS-IM performance requirements in TS 38.101-4 |
Huawei, HiSilicon |
| R4-2220275 |
CR for Maintenance of PDSCH demod requirements with inter-cell interference |
Apple |
| R4-2220279 |
CR on maintenance on PDSCH 4Rx demod requirements for MU-MIMO IRC |
China Telecom |
| 5.5 |
Home gNB RF requirements |
|
| R4-2218652 |
Draft CR for 38.104: define home class as one kind of LA BS |
CMCC |
| R4-2220263 |
CR for 38.104: define home class as one kind of LA BS |
CMCC |
| 5.6 |
MIMO OTA and FR1 TRP TRS requirements |
|
| R4-2218108 |
On device pool considerations for TRP TRS |
Apple |
| R4-2218841 |
Discussions on UE information collection for Rel-17 TRP TRS |
vivo |
| R4-2218842 |
CR to TS 38.161 on test parameters |
vivo |
| R4-2218843 |
CR to TS 38.151 on FR2 MU |
vivo |
| 5.7 |
Moderator summary and conclusions |
|
| R4-2220049 |
Topic summary for [105][203] R17_maintenance_RRM |
Moderator (Intel) |
| R4-2220082 |
Topic summary for [105][102] R17_UERF_maintenance |
Moderator (Ericsson) |
| R4-2220127 |
Summary for [105][301] BSRF_maintenance |
Moderator (Ericsson) |
| R4-2220143 |
Summary for [105][317] Demod_Maintenance |
Moderator (Apple) |
| R4-2220525 |
Ad hoc minutes for R17 UE RF maintenance |
Ericsson |
| R4-2220526 |
WF on New IEs for maximum aggregated BW for intra-band CA and for inter-band CA for FR1 |
Qualcomm |
| R4-2220819 |
WF on New IEs for maximum aggregated BW for intra-band CA and for inter-band CA for FR1 |
Qualcomm |
| 6.1.1 |
RF core maintenance |
|
| R4-2218894 |
CR to 38.106: ACLR requirements |
NEC |
| R4-2218895 |
TP to 38.115-1: ACLR requirement |
NEC |
| R4-2218896 |
TP to 38.115-2: OTA ACLR requirement |
NEC |
| R4-2218897 |
CR to 38.106: EVM requirements |
NEC |
| R4-2218898 |
TP to 38.115-1: EVM requirement |
NEC |
| R4-2218899 |
TP to 38.115-2: OTA EVM requirement |
NEC |
| R4-2218900 |
CR to 38.106: ACRR requirements |
NEC |
| R4-2218901 |
TP to 38.115-1: ACRR requirement |
NEC |
| R4-2218902 |
TP to 38.115-2: OTA ACRR requirement |
NEC |
| R4-2220213 |
CR to 38.106: ACLR requirements |
NEC |
| R4-2220214 |
TP to 38.115-1: ACLR requirement |
NEC |
| R4-2220215 |
TP to 38.115-2: OTA ACLR requirement |
NEC |
| R4-2220216 |
CR to 38.106: EVM requirements |
NEC |
| R4-2220217 |
TP to 38.115-1: EVM requirement |
NEC |
| R4-2220218 |
TP to 38.115-2: OTA EVM requirement |
NEC |
| R4-2220269 |
CR to 38.106: ACRR requirements |
NEC |
| R4-2220270 |
TP to 38.115-1: ACRR requirement |
NEC |
| R4-2220271 |
TP to 38.115-2: OTA ACRR requirement |
NEC |
| 6.1.2 |
EMC core requirement maintenance and performance requirements |
|
| R4-2218615 |
CR to TS 38.114 repeater performance criteria R17 |
ZTE Corporation |
| R4-2218616 |
Discussion on repeater EMC performance criteria |
ZTE Corporation |
| R4-2219344 |
CR to TS 38.114 Clause 4.5 |
Ericsson |
| R4-2220220 |
CR to TS 38.114 repeater performance criteria R17 |
ZTE Corporation |
| R4-2220221 |
CR to TS 38.114 Clause 4.5 |
Ericsson |
| R4-2220222 |
Discussion on repeater EMC performance criteria |
ZTE |
| 6.1.3.1.1 |
Stimulus signal /Test models |
|
| R4-2218485 |
Discussion of the remaining issues for repeater |
CATT |
| R4-2219453 |
Repeater stimulus signal spectral purity annex and TP |
Keysight Technologies UK Ltd |
| 6.1.3.1.2 |
Others |
|
| R4-2219454 |
Repeater EVM measurement |
Keysight Technologies UK Ltd |
| 6.1.3.2 |
Conductive conformance Testing |
|
| R4-2218419 |
TS 38.115-1 v0.3.0 |
CATT |
| R4-2218486 |
Correction TP for TS 38.115-1 |
CATT |
| R4-2219643 |
Spectral purity for FR1 |
Ericsson |
| R4-2219644 |
Draft CR to 38.115-1: Spectrum purity |
Ericsson |
| R4-2220225 |
WF for Repeater conformance test |
Ericsson |
| R4-2220226 |
Draft CR to 38.115-1: Spectrum purity |
Ericsson |
| 6.1.3.3 |
Radiated conformance Testing |
|
| R4-2218700 |
TP for TS 38.115-2 OTA Out of band gain requirements |
NTT DOCOMO, INC. |
| R4-2219347 |
Maintenance TP for TS 38.115-2 |
ZTE Corporation |
| R4-2219348 |
TS 38.115-2 v0.3.0 |
ZTE Corporation |
| R4-2219645 |
Spectrum purity for FR2 |
Ericsson |
| R4-2219646 |
Draft CR to 38.115-2: Spectrum purity |
Ericsson |
| R4-2220227 |
Draft CR to 38.115-2: Spectrum purity |
Ericsson |
| R4-2220228 |
TP for TS 38.115-2 OTA Out of band gain requirements |
NTT DOCOMO, INC. |
| R4-2220289 |
Maintenance TP for TS 38.115-2 |
ZTE Corporation |
| 6.1.4 |
Moderator summary and conclusions |
|
| R4-2220128 |
Summary for [105][302] NR_Repeater_RFMaintenance |
Moderator (Nokia) |
| R4-2220129 |
Summary for [105][303] NR_Repeater_RFConformance |
Moderator (CATT) |
| 6.2.1 |
System parameters and Satellite Access Node RF requirement maintenance |
|
| R4-2218456 |
Further discussion on RF Maintenance for NTN SAN |
CATT |
| R4-2218457 |
CR for TS 38.108, Correct unwanted emission requirements applicability for SAN type 1-H |
CATT |
| R4-2218458 |
CR for TS 38.108, Remove co-location requirement related content |
CATT |
| R4-2218459 |
CR for TS 38.108, On operating band unwaned emission requirement |
CATT |
| R4-2218501 |
NTN - Discussion on remaining open issues |
Ericsson |
| R4-2218502 |
CR to TS 38.108 - Updates related to DfOBUE |
Ericsson |
| R4-2219137 |
Discussion on synchronization raster ambiguity in NTN |
Qualcomm Incorporated |
| R4-2219281 |
Discussion on SAN OBUE and Spurious Emission Limits |
THALES |
| R4-2219608 |
CR for TR 38.863 to maintain SAN parts |
Huawei, HiSilicon |
| R4-2219609 |
Discussion on definition of delta FOBUE |
Huawei, HiSilicon |
| R4-2219610 |
CR for 38.108 to maintain unwanted emissions clause |
Huawei, HiSilicon |
| R4-2219967 |
Discussion on the colocation requirements consideration for SAN RF |
Huawei, HiSilicon |
| R4-2219968 |
CR to TS 38.108: removal of colocation requirements |
Huawei, HiSilicon |
| R4-2220163 |
Description of general performance part sections for SAN TS 38.108 |
THALES |
| 6.2.2.1 |
General |
|
| R4-2218455 |
TS 38.181 v0.3.0 NR Satellite Access Node (SAN) conformance testing |
CATT |
| R4-2218462 |
TP for TS 38.181 – Clause 4.1.2 Acceptable uncertainty of Test System |
CATT |
| R4-2219461 |
TP for TS 38.181 - Annex D Updates |
THALES |
| R4-2219834 |
TP for TS 38.181: Annex B |
Ericsson |
| R4-2219835 |
TP for TS 38.181: Annex C |
Ericsson |
| R4-2219836 |
TP for TS 38.181: Annex E |
Ericsson |
| R4-2219837 |
TP for TS 38.181: Annex J |
Ericsson |
| R4-2220230 |
TP for TS 38.181 - Annex D Updates |
THALES |
| R4-2220231 |
TP for TS 38.181: Annex B |
Ericsson |
| R4-2220232 |
TP for TS 38.181: Annex E |
Ericsson |
| R4-2220233 |
TP for TS 38.181: Annex J |
Ericsson |
| R4-2220290 |
TP for TS 38.181 – Clause 4.1.2 Acceptable uncertainty of Test System |
CATT |
| R4-2220292 |
TP for TS 38.181 – DUT size for applicable MU values |
Huawei |
| R4-2220293 |
TP for TS 38.181: Annex J |
Ericsson |
| 6.2.2.2 |
Conductive conformance Testing |
|
| R4-2219469 |
TP for TS 38.181 - Clause 6.5 Transmitted signal quality |
THALES |
| R4-2219490 |
TP for TS 38.181 - Corrections to Clause 6.6 Unwanted emissions |
THALES |
| R4-2220038 |
Inputs to the discussion on the extreme conditions testing, and suitability of the OTA test chambers |
Huawei, HiSilicon |
| R4-2220234 |
TP for TS 38.181 - Clause 6.5 Transmitted signal quality |
THALES |
| R4-2220305 |
TP for TS 38.181 - Corrections to Clause 6.6 Unwanted emissions |
THALES |
| 6.2.2.3 |
Radiated conformance Testing |
|
| R4-2218460 |
Further discussion on conformance testing for NTN SAN |
CATT |
| R4-2218461 |
TP for TS 38.181: Remove co-location requirement related content |
CATT |
| R4-2219647 |
TP for TS 38.181 - Clause 9.6 OTA transmitted signal quality |
THALES |
| R4-2219650 |
TP for TS 38.181 - Clause 9.7.5 OTA transmitter spurious emissions |
THALES |
| R4-2219651 |
TP for TS 38.181 - Clauses 9.2 Radiated transmit power and 9.3 OTA SAN output power |
THALES |
| R4-2219679 |
TP for TS 38.181 - Corrections to Clause 9.7 OTA unwanted emissions |
THALES |
| R4-2219833 |
TP for TS 38.181: clause 10.3 OTA refsens |
Ericsson |
| R4-2219969 |
TP to TS 38.181: removal of colocation requirements |
Huawei, HiSilicon |
| R4-2220235 |
TP for TS 38.181: Remove co-location requirement related content |
CATT, Huawei |
| R4-2220236 |
TP for TS 38.181 - Clause 9.6 OTA transmitted signal quality |
THALES |
| R4-2220237 |
TP for TS 38.181 - Clause 9.7.5 OTA transmitter spurious emissions |
THALES |
| R4-2220238 |
TP for TS 38.181 - Clauses 9.2 Radiated transmit power and 9.3 OTA SAN output power |
THALES, CATT |
| R4-2220306 |
TP for TS 38.181 - Corrections to Clause 9.7 OTA unwanted emissions |
THALES |
| 6.2.3 |
UE RF requirement maintenance |
|
| R4-2218110 |
CR to 38.101-5 for NTN UE RF requirements corrections |
Apple |
| R4-2218111 |
CR to 38.101-5 on 64QAM requirements related corrections |
Apple |
| R4-2219043 |
CR to 38.101-5: Corrections on reference for NTN UE |
Xiaomi |
| R4-2219308 |
FCC Part §25.202(f) discussion and implications on SEM, spurious emissions requirements for NR NTN UE |
Ligado Networks |
| R4-2219328 |
CR to include additional emission requirements related to FCC Part 25.202(f) |
Ligado Networks |
| R4-2220571 |
CR to 38.101-5 for NTN UE RF requirements corrections |
Apple |
| R4-2220572 |
CR to 38.101-5 on 64QAM requirements related corrections |
Apple |
| R4-2220820 |
CR to 38.101-5 for NTN UE RF requirements corrections |
Apple |
| 6.2.4 |
RRM core requirement maintenance |
|
| R4-2218659 |
Discussion on RRM core requirements for NTN |
CMCC |
| 6.2.4.1 |
Measurement procedure requirements |
|
| R4-2218136 |
On measurement procedure for NTN UE |
Apple |
| R4-2218226 |
Discussion on measurement procedure requirements in NTN |
MediaTek inc. |
| R4-2218426 |
Discussion on remaining issues of core requirements for NTN RRM |
CATT |
| R4-2218427 |
Introducing clarification for UE acquiring system information during handover |
CATT |
| R4-2218573 |
Discussion on the remaining issues for NTN RRM |
Xiaomi |
| R4-2218574 |
CR on cell reselection requirements with relaxed measurement criterion for satellite access |
Xiaomi |
| R4-2218991 |
Discussion on measurement procedure for NR NTN |
OPPO |
| R4-2219026 |
CR on intra-frequency measurements in NTN |
Samsung |
| R4-2219067 |
Measurement procedure requirements |
Ericsson |
| R4-2219477 |
CR on Clarification of Ttrigger Requirements for Cell Reselection |
Nokia, Nokia Shanghai Bell |
| R4-2219478 |
Discussion about RAN2 LS on enhanced cell reselection criteria. |
Nokia, Nokia Shanghai Bell |
| R4-2219537 |
reply LS on enhanced cell reselection requirements |
Huawei, HiSilicon |
| R4-2219538 |
CR on L1-RSRP measurement requirements |
Huawei, HiSilicon |
| R4-2219539 |
CR on MG requirements for NTN |
Huawei, HiSilicon |
| R4-2220314 |
CR on MG requirements for NTN |
Huawei, HiSilicon |
| R4-2220315 |
CR on L1-RSRP measurement requirements |
Huawei, HiSilicon |
| R4-2220456 |
CR on cell reselection requirements with relaxed measurement criterion for satellite access |
Xiaomi |
| 6.2.4.2 |
Others |
|
| R4-2219025 |
CR on intra-frequency cell reselection in NTN |
Samsung |
| R4-2219065 |
CR on correction to CHO requirement for satellite access |
Ericsson |
| R4-2219066 |
CR on correction to cell re-selection requirement for satellite access |
Ericsson |
| R4-2219479 |
CR on Re-establishment Requirements for NTN |
Nokia, Nokia Shanghai Bell |
| R4-2219480 |
Discussion about HO Requirements in NTN |
Nokia, Nokia Shanghai Bell |
| R4-2219534 |
Discussion on other requirements for NTN RRM |
Huawei, HiSilicon |
| R4-2219535 |
CR on RRC re-establishment requirements for NTN |
Huawei, HiSilicon |
| R4-2219536 |
CR on HO requirements for NTN |
Huawei, HiSilicon |
| R4-2220316 |
CR on HO requirements for NTN |
Huawei, HiSilicon |
| R4-2220457 |
CR on correction to CHO requirement for satellite access |
Ericsson |
| R4-2220709 |
CR on correction to cell re-selection requirement for satellite access |
Ericsson |
| R4-2220710 |
CR on RRC re-establishment requirements for NTN |
Huawei, HiSilicon |
| 6.2.5.1 |
General |
|
| R4-2218407 |
Open Issues in UE and Satellite position details |
Qualcomm Incorporated |
| R4-2218428 |
Discussion on performance requirements for NTN RRM |
CATT |
| R4-2218660 |
Discussion on RRM test cases for NTN |
CMCC |
| R4-2219068 |
Performance procedure requirements |
Ericsson |
| R4-2219481 |
Discussion on SAN Configurations for Test Cases |
Nokia, Nokia Shanghai Bell |
| R4-2219540 |
Discussion on test cases for NTN |
Huawei, HiSilicon |
| R4-2219541 |
draftCR on general requirement for NTN RRM test cases |
Huawei, HiSilicon |
| R4-2220313 |
WF on Rel-17 NR NTN RRM Core Requirements maintenance |
Qualcomm |
| R4-2220413 |
Big CR for NR NTN RRM performance requirements |
Qualcomm |
| R4-2220424 |
draftCR on general requirement for NTN RRM test cases |
Huawei, HiSilicon |
| R4-2220425 |
LS to RAN2 on inter-operability testing (IOT) bit for inter-satellite measurement |
MediaTek |
| R4-2220426 |
Reply LS on enhanced cell reselection requirements |
Huawei |
| R4-2220427 |
LS on capability description for enhanced cell reselection requirements in NTN |
Nokia |
| R4-2220741 |
Reply LS on enhanced cell reselection requirements |
Huawei |
| 6.2.5.2 |
Test cases for Cell reselection to intra- and inter-frequency neighbor cell |
|
| R4-2218912 |
Draft CR on test case for cell reselection to FR1 inter-frequency NR cell for satellite access |
LG Electronics UK |
| R4-2219482 |
Discussion on SIB19 acquisition for Cell Reselection Performance |
Nokia, Nokia Shanghai Bell |
| R4-2220421 |
Draft CR on test case for cell reselection to FR1 inter-frequency NR cell for satellite access |
LG Electronics UK |
| 6.2.5.4 |
Test cases for Intra- and inter-frequency CHO |
|
| R4-2218429 |
Modification on test cases for NTN conditional handover |
CATT |
| R4-2220390 |
Modification on test cases for NTN conditional handover |
CATT |
| 6.2.5.5 |
Test cases for UE transmit timing |
|
| R4-2218661 |
Draft CR on timing advance adjustment accuracy test for NTN |
CMCC |
| R4-2219243 |
Discussion on remaining issues on test cases for NTN UE timing |
Huawei, HiSilicon |
| R4-2219244 |
DraftCR on UE transmit timing tests for NTN |
Huawei, HiSilicon |
| R4-2219483 |
Test Case Configuration for UE Transmit Timing |
Nokia, Nokia Shanghai Bell |
| R4-2220420 |
Draft CR on timing advance adjustment accuracy test for NTN |
CMCC |
| R4-2220423 |
DraftCR on UE transmit timing tests for NTN |
Huawei, HiSilicon |
| 6.2.5.6 |
Test cases for RLM and BFR |
|
| R4-2218662 |
Draft CR on test cases for CSI-RS based RLM for NTN |
CMCC |
| R4-2219069 |
draft CR on test cases of BFD and LR for SA |
Ericsson |
| R4-2220422 |
draft CR on test cases of BFD and LR for SA |
Ericsson |
| 6.2.5.8 |
Test cases for Inter-frequency measurement delay |
|
| R4-2218227 |
CR on test cases for Inter-frequency measurement delay for satellite access with gap |
MediaTek inc. |
| R4-2220418 |
CR on test cases for Inter-frequency measurement delay for satellite access with gap |
MediaTek inc. |
| 6.2.5.10 |
Test cases for RRM measurement accuracy |
|
| R4-2218228 |
CR on test cases for Measurement Accuracy for SS-RSRQ for satellite access |
MediaTek inc. |
| R4-2220419 |
CR on test cases for Measurement Accuracy for SS-RSRQ for satellite access |
MediaTek inc. |
| 6.2.6.1 |
General |
|
| R4-2218711 |
Discussion on general for NTN demodulation requirements |
Ericsson |
| R4-2219484 |
Discussion on NTN demodulation requirements - general |
Nokia, Nokia Shanghai Bell |
| R4-2220857 |
Big CR for UE NTN performance requirements (TS38.101-5, Rel-17, CAT B) |
Samsung |
| 6.2.6.2 |
Satellite Access Node demodulation requirements |
|
| R4-2219342 |
Description of general performance part sections for SAN TS 38.108 |
THALES |
| R4-2219447 |
TP for TS 38.181 - Clauses 8.1 and 11.1 General performance parts |
THALES |
| R4-2219664 |
Draft CR on propagation conditions of NTN SAN performance requirements (TS38.108, Rel-17) |
Huawei, HiSilicon |
| R4-2219665 |
pCR on FRC of NTN SAN performance requirements (TS38.181, Rel-17) |
Huawei, HiSilicon |
| R4-2219673 |
Summary of NTN SAN simulation results |
Huawei, HiSilicon |
| R4-2219674 |
Big CR on NTN SAN performance requirements (TS38.108, Rel-17) |
Huawei, HiSilicon |
| R4-2220162 |
TP for TS 38.181 - Clauses 8.1 and 11.1 General performance parts |
THALES |
| R4-2220164 |
Draft CR on propagation conditions of NTN SAN performance requirements (TS38.108, Rel-17) |
Huawei, HiSilicon |
| 6.2.6.2.1 |
PUSCH requirements |
|
| R4-2218712 |
Discussion on SAN PUSCH demodulation requirements |
Ericsson |
| R4-2218715 |
draft CR for TS38.108 FRC tables for SAN PUSCH demodulation requirements |
Ericsson |
| R4-2218717 |
TP for TS 38.181 SAN PUSCH demodulation requirements |
Ericsson |
| R4-2219017 |
Simulation results on PUSCH demodulation requirement for Rel-17 NTN |
Samsung |
| R4-2219485 |
Simulation results for NTN SAN PUSCH demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2219663 |
Draft CR on NTN SAN PUSCH performance requirements (TS38.108, Rel-17) |
Huawei, HiSilicon |
| R4-2219668 |
pCR on NTN SAN PUSCH performance requirements (TS38.181, Rel-17) |
Huawei, HiSilicon |
| R4-2219669 |
Discussion on satellite NTN demod PUSCH |
Huawei, HiSilicon |
| R4-2219672 |
Simulation results on satellite NTN demod PUSCH |
Huawei, HiSilicon |
| R4-2220165 |
TP for TS 38.181 SAN PUSCH demodulation requirements |
Ericsson |
| R4-2220166 |
Draft CR on NTN SAN PUSCH performance requirements (TS38.108, Rel-17) |
Huawei, HiSilicon |
| R4-2220167 |
pCR on NTN SAN PUSCH performance requirements (TS38.181, Rel-17) |
Huawei, HiSilicon |
| 6.2.6.2.2 |
PUCCH requirements |
|
| R4-2218713 |
Discussion on SAN PUCCH demodulation requirements |
Ericsson |
| R4-2218714 |
simulation results for SAN PUCCH demodulation requirements |
Ericsson |
| R4-2218716 |
draft CR for TS38.108 SAN PUCCH demodulation requirements |
Ericsson |
| R4-2218718 |
TP for TR38.181 SAN PUCCH demodulation radiated requirements |
Ericsson |
| R4-2219018 |
Discussion and simulation results on PUCCH demodulation requirement for Rel-17 NTN |
Samsung |
| R4-2219486 |
Simulation results for NTN SAN PUCCH demodulation |
Nokia, Nokia Shanghai Bell |
| R4-2219667 |
pCR on NTN SAN PUCCH performance requirements (TS38.181, Rel-17) |
Huawei, HiSilicon |
| R4-2219671 |
Simulation results on satellite NTN demod PUCCH |
Huawei, HiSilicon |
| R4-2220168 |
draft CR for TS38.108 SAN PUCCH demodulation requirements |
Ericsson |
| R4-2220169 |
TP for TR38.181 SAN PUCCH demodulation radiated requirements |
Ericsson |
| R4-2220170 |
pCR on NTN SAN PUCCH performance requirements (TS38.181, Rel-17) |
Huawei, HiSilicon |
| 6.2.6.2.3 |
PRACH requirements |
|
| R4-2218719 |
TP for TR38.181 SAN PRACH demodulation conducted requirements |
Ericsson |
| R4-2219019 |
Simulation results on PRACH demodulation requirement for Rel-17 NTN |
Samsung |
| R4-2219662 |
Draft CR on NTN SAN PRACH performance requirements (TS38.108, Rel-17) |
Huawei, HiSilicon |
| R4-2219666 |
pCR on NTN SAN PRACH performance requirements (TS38.181, Rel-17) |
Huawei, HiSilicon |
| R4-2219670 |
Simulation results on satellite NTN demod PRACH |
Huawei, HiSilicon |
| R4-2220171 |
TP for TR38.181 SAN PRACH demodulation conducted requirements |
Ericsson |
| R4-2220172 |
Draft CR on NTN SAN PRACH performance requirements (TS38.108, Rel-17) |
Huawei, HiSilicon |
| R4-2220173 |
pCR on NTN SAN PRACH performance requirements (TS38.181, Rel-17) |
Huawei, HiSilicon |
| 6.2.6.3.1 |
PDSCH requirements |
|
| R4-2218064 |
Views on NTN UE PDSCH Requirements |
Qualcomm Incorporated |
| R4-2218065 |
Simulation Results on NTN UE PDSCH Demodulation Requirements |
Qualcomm Incorporated |
| R4-2218066 |
Summary of Simulation Results for NTN UE Demodulation |
Qualcomm Incorporated |
| R4-2218178 |
On PDSCH demod requirements for NTN |
Apple |
| R4-2218243 |
Simulation results for NR-NTN PDSCH requirements |
MediaTek inc. |
| R4-2218370 |
Draft CR on PDSCH demodulation requirements for NTN UE |
Qualcomm Incorporated |
| R4-2219278 |
Update simulation results for UE PDSCH for NTN |
Ericsson |
| R4-2219487 |
Simulation results on PDSCH demodulation requirements for NTN |
Nokia, Nokia Shanghai Bell |
| R4-2219488 |
Discussion on testing of PDSCH disabled HARQ requirements for NTN |
Nokia, Nokia Shanghai Bell |
| R4-2219675 |
Draft CR on applicability rules of UE NTN performance requirements (TS38.101-5, Rel-17) |
Huawei, HiSilicon |
| R4-2219676 |
Draft CR on general part of UE NTN performance requirements (TS38.101-5, Rel-17) |
Huawei, HiSilicon |
| R4-2219677 |
Discussion on UE NTN demod PDSCH |
Huawei, HiSilicon |
| R4-2219678 |
Simulation results on satellite NTN demod PDSCH |
Huawei, HiSilicon |
| R4-2220159 |
Draft CR on PDSCH demodulation requirements for NTN UE |
Qualcomm Incorporated |
| R4-2220160 |
Draft CR on applicability rules of UE NTN performance requirements (TS38.101-5, Rel-17) |
Huawei, HiSilicon |
| 6.2.7 |
Moderator summary and conclusions |
|
| R4-2220050 |
Topic summary for [105][204] NR_NTN_solutions_RRM_1 |
Moderator (Qualcomm) |
| R4-2220051 |
Topic summary for [105][205] NR_NTN_solutions_RRM_2 |
Moderator (Xiaomi) |
| R4-2220130 |
Summary for [105][304] NTN_Solutions_RF_Maintenance |
Moderator (Thales) |
| R4-2220131 |
Summary for [105][305] NTN_Solutions_RFConformance |
Moderator (Ericsson) |
| R4-2220144 |
Summary for [105][318] NR_NTN_Demod_Part1 |
Moderator (Qualcomm) |
| R4-2220145 |
Summary for [105][319] NR_NTN_Demod_Part2 |
Moderator (Huawei) |
| R4-2220158 |
WF for NTN UE demodulation part |
Qualcomm |
| R4-2220161 |
WF for NTN BS demodulation part |
Huawei, HiSilicon |
| R4-2220229 |
WF for Rel-17 SAN RF maintenance |
THALES |
| R4-2220282 |
WF for NTN UE demodulation par |
Qualcomm |
| R4-2220291 |
WF for Rel-17 SAN RF maintenance |
THALES |
| 6.3.1 |
Operation bands, system parameter and UE RF maintenance |
|
| R4-2219814 |
Adding DL RMC for band n263 |
Huawei, HiSilicon |
| R4-2219896 |
60 GHz UE PTRS capabilities |
Qualcomm |
| R4-2219899 |
CR to 38.101-2 on 60GHz EVM PTRS capability |
Qualcomm |
| R4-2220026 |
System parameters maintenance for FR2-2 |
Intel Corporation |
| R4-2220576 |
Adding DL RMC for band n263 |
Huawei, HiSilicon |
| R4-2220821 |
Adding DL RMC for band n263 |
Huawei, HiSilicon |
| 6.3.2 |
BS RF requirements maintenance |
|
| R4-2218319 |
CR to TS 38.104 on tables for BS channel bandwidths |
Nokia, Nokia Shanghai Bell, NTT DoCoMo |
| R4-2218701 |
CR for TS38.104 editorial correction on CBW and SCS per operating band |
NTT DOCOMO, INC. |
| 6.3.3.1 |
General |
|
| R4-2218320 |
Draft CR to TS 38.141-2 in clauses 6.3 to 6.5 for extending current NR operation to 71GHz |
Nokia, Nokia Shanghai Bell |
| R4-2218834 |
On general aspects relevant for FR2-2 conformance testing |
Ericsson |
| R4-2218837 |
Draft CR to TS 38.141-2: Addition of FR2-2 aspects in clause 4 |
Ericsson |
| R4-2219449 |
FR2-2 Power measurement equipment MU with Mixer for BS conformance testing |
Keysight Technologies UK Ltd |
| R4-2219450 |
FR2-2 Test equipment MU for BS conformance testing |
Keysight Technologies UK Ltd |
| R4-2219451 |
DraftCR to 37.941: 71 GHz Extension TE MU update |
Keysight Technologies UK Ltd |
| R4-2219843 |
FR2-2 BS conformance test consideration |
Keysight Technologies UK Ltd |
| R4-2220201 |
Draft CR to TS 38.141-2 in clauses 6.3 to 6.5 for extending current NR operation to 71GHz |
Nokia, Nokia Shanghai Bell |
| R4-2220202 |
Draft CR to TS 38.141-2: Addition of FR2-2 aspects in clause 4 |
Ericsson |
| R4-2220203 |
DraftCR to 37.941: 71 GHz Extension TE MU update |
Keysight Technologies UK Ltd |
| R4-2220205 |
FR2-2 Test equipment MU for BS conformance testing |
Keysight Technologies UK Ltd |
| R4-2220287 |
Draft CR to TS 38.141-2: Addition of FR2-2 aspects in clause 4 |
Ericsson |
| 6.3.3.2 |
Transmitter characteristics |
|
| R4-2218321 |
Proposals on measurement uncertainty of BS OTA transmitter requirements for extending current NR operation to 71 GHz |
Nokia, Nokia Shanghai Bell |
| R4-2218833 |
Draft CR to TR 37.941: Addition of aspects related to EIRP measurement in CATR relevant for FR2-2 in sub-clause 7.3, 8.3, 9.2.3 and 9.2.7 |
Ericsson |
| R4-2218835 |
On aspects related to FR2-2 transmitter conformance testing |
Ericsson |
| R4-2218908 |
Discussion on OBW measurements for FR2-2 |
NEC |
| R4-2218909 |
CR to 38.141-2: OTA OBW requirements for FR2-2 |
NEC |
| R4-2219452 |
draftCR to 38.141-2: 71 GHz Extension BS EVM Clause 6.6 and Annex L (6.6, L) |
Keysight Technologies UK Ltd |
| R4-2219970 |
draft CR to TS 38.141-2 on FR2-2 implementation (sections 1,2,3,6.7.1, 6.7.2, 6.7.3, 6.7.4, 7.6) |
Huawei, HiSilicon |
| R4-2220200 |
draftCR to 38.141-2: OTA OBW requirements for FR2-2 |
NEC |
| R4-2220204 |
draftCR to 38.141-2: 71 GHz Extension BS EVM Clause 6.6 and Annex L (6.6, L) |
Keysight Technologies UK Ltd |
| R4-2220206 |
draft CR to TS 38.141-2 on FR2-2 implementation (sections 1,2,3,6.7.1, 6.7.2, 6.7.3, 6.7.4, 7.6) |
Huawei, HiSilicon |
| R4-2220207 |
Draft CR to TR 37.941: Addition of aspects related to EIRP measurement in CATR relevant for FR2-2 in sub-clause 7.3, 8.3, 9.2.3 and 9.2.7 |
Ericsson |
| 6.3.3.3 |
Receiver characteristics |
|
| R4-2218322 |
Proposals on measurement uncertainty of BS OTA receiver requirements for extending current NR operation to 71 GHz |
Nokia, Nokia Shanghai Bell |
| R4-2218463 |
Draft CR for 38.141-2, On FR2-2 BS RF conformance testings in clauses 7.1-7.5 and respective MU and TT |
CATT |
| R4-2218464 |
Draft CR for 37.941, On FR2-2 RX directional requirements in clauses 10.1-10.5 and respective MU and TT summary |
CATT |
| R4-2218836 |
On aspects related to FR2-2 receiver conformance testing |
Ericsson |
| R4-2218838 |
Draft CR to TR 37.941: Addition of aspects related to EIS measurement in CATR relevant for FR2-2 in sub-clause 10.2.3 and sub-clause 10.2.7 |
Ericsson |
| R4-2219345 |
draft CR to TS38.141-2 Clause 7.7, 7.8 |
ZTE Corporation |
| R4-2219346 |
draft CR to TS38.141-2 Clause 7.9 |
ZTE Corporation |
| R4-2220208 |
Draft CR for 38.141-2, On FR2-2 BS RF conformance testings in clauses 7.1-7.5 and respective MU and TT |
CATT |
| R4-2220209 |
Draft CR for 37.941, On FR2-2 RX directional requirements in clauses 10.1-10.5 and respective MU and TT summary |
CATT |
| R4-2220210 |
Draft CR to TR 37.941: Addition of aspects related to EIS measurement in CATR relevant for FR2-2 in sub-clause 10.2.3 and sub-clause 10.2.7 |
Ericsson |
| R4-2220211 |
draft CR to TS38.141-2 Clause 7.7, 7.8 |
ZTE Corporation |
| R4-2220212 |
draft CR to TS38.141-2 Clause 7.9 |
ZTE Corporation |
| R4-2220307 |
big draft CR to TS38.141-2 FR2-2 RF conformance introduction |
Huawei |
| 6.3.4 |
RRM core requirement maintenance |
|
| R4-2218162 |
RRM core requirement maintenance for NR operation in 52.6GHz - 71GHz |
Apple |
| R4-2218163 |
CR on TCI assumption for RSSI measurement for FR2-2 |
Apple |
| R4-2218229 |
Discussion on RRM requirements for FR2-2 |
MediaTek inc. |
| R4-2218591 |
Discussion on QCL assumption for Inter-frequency RSSI measurement |
LG Electronics Inc. |
| R4-2218592 |
CR on QCL-ed assumption for inter-frequency RSSI measurement in FR2-2 |
LG Electronics Inc. |
| R4-2219064 |
LBT impacts on RRM requirements for extending NR operation to 71GHz |
Ericsson |
| R4-2219222 |
CR on cell reselection requirements for FR2-2 |
Huawei, HiSilicon |
| R4-2219223 |
CR on QCL assumptions of inter-frequency measurement for FR2-2 |
Huawei, HiSilicon |
| R4-2219224 |
Discussion on general requirements on FR2-2 |
Huawei, HiSilicon |
| R4-2220030 |
Remaining issues for FR2-2 RRM |
Qualcomm Incorporated |
| R4-2220042 |
CR on Measurement Procedures |
Qualcomm Incorporated |
| R4-2220319 |
CR on QCL-ed assumption for inter-frequency RSSI measurement in FR2-2 |
LG Electronics Inc. |
| R4-2220320 |
CR on Measurement Procedures |
Qualcomm Incorporated |
| 6.3.5.1 |
General (Test configurations, side conditions and spec structure) |
|
| R4-2218230 |
Discussion on test for RRM requirements in FR2-2 with CCA |
MediaTek inc. |
| R4-2218470 |
Further discussion on general RRM performance requirements for FR2-2 |
CATT |
| R4-2218932 |
Discussion on RRM performance requirements with CCA in FR2-2 |
Nokia, Nokia Shanghai Bell |
| R4-2219225 |
Discussion on performance requirements for FR2-2 |
Huawei, HiSilicon |
| R4-2220317 |
WF on Rel-17 NR NTN RRM Performance requirements |
Xiaomi |
| R4-2220318 |
WF on Rel-17 NR extension to 71GHz RRM Core requirements maintenance |
Huawei |
| R4-2220321 |
WF on Rel-17 NR extension to 71GHz RRM Performance requirements |
Huawei |
| R4-2220711 |
WF on Rel-17 NR NTN RRM Performance requirements |
Xiaomi |
| 6.3.5.2 |
Test cases with and without CCA |
|
| R4-2220045 |
Big CR for NR operation to 71GHz RRM performance requirements |
MCC, Qualcomm |
| 6.3.5.2.2 |
Test cases for RRC_CONNECTED mobility |
|
| R4-2218933 |
Draft CR on RRC connected mobility test cases in FR2-2 |
Nokia, Nokia Shanghai Bell |
| R4-2219226 |
DraftCR on HO test cases for FR2-2 with CCA |
Huawei, HiSilicon |
| R4-2220044 |
Draft CR on TC - RRC Connection Release with re-direction |
Qualcomm Incorporated |
| 6.3.5.2.3 |
Test cases for timing |
|
| R4-2218934 |
CR on corrections to timing test cases in FR2-2 |
Nokia, Nokia Shanghai Bell |
| R4-2219227 |
DraftCR on timing test cases for FR2-2 with CCA |
Huawei, HiSilicon |
| R4-2219228 |
DraftCR on timing test cases for FR2-2 |
Huawei, HiSilicon |
| R4-2220449 |
CR on corrections to timing test cases in FR2-2 |
Nokia, Nokia Shanghai Bell |
| 6.3.5.2.4 |
Test cases for signaling characteristics |
|
| R4-2218471 |
Draft CR on test cases for beam failure detection and link recovery with CCA for FR2-2 |
CATT |
| R4-2218472 |
Draft CR on test cases for SCell Activation and deactivation for SCell in FR2 in non-DRX with CCA for FR2-2 |
CATT |
| R4-2218473 |
Draft CR on test cases for SCell Activation and deactivation for FR1+FR2 inter-band with target SCell in FR2 with CCA for FR2-2 |
CATT |
| R4-2219063 |
RLM test cases for 71GHz with CCA |
Ericsson |
| R4-2219229 |
DraftCR on signaling characteristics test cases for FR2-2 |
Huawei, HiSilicon |
| R4-2220043 |
Draft CR on TC - PSCell addition and release delay |
Qualcomm Incorporated |
| R4-2220445 |
Draft CR on test cases for beam failure detection and link recovery with CCA for FR2-2 |
CATT |
| R4-2220446 |
Draft CR on test cases for SCell Activation and deactivation for SCell in FR2 in non-DRX with CCA for FR2-2 |
CATT |
| R4-2220447 |
Draft CR on test cases for SCell Activation and deactivation for FR1+FR2 inter-band with target SCell in FR2 with CCA for FR2-2 |
CATT |
| R4-2220450 |
RLM test cases for 71GHz with CCA |
Ericsson |
| R4-2220451 |
DraftCR on signaling characteristics test cases for FR2-2 |
Huawei, HiSilicon |
| 6.3.5.2.5 |
Test cases for measurement |
|
| R4-2218773 |
Draft CR on introduction of intra-frequency and inter-frequency measurement test cases with CCA for FR2-2 |
vivo |
| R4-2218774 |
Draft CR on introduction of intra-frequency and inter-frequency measurement test cases without CCA for FR2-2 |
vivo |
| R4-2220448 |
Draft CR on introduction of intra-frequency and inter-frequency measurement test cases with CCA for FR2-2 |
vivo |
| 6.3.6.1 |
General (incl. Channel models) |
|
| R4-2219514 |
Big CR on FR2-2 UE demodulation performance requirements in TS 38.101-4 |
Huawei, HiSilicon |
| R4-2219747 |
Big CR to 38.104: demodulation requirements introduction for FR2-2 |
Nokia, Nokia Shanghai Bell, Intel |
| R4-2219748 |
Big CR to 38.141-2: demodulation requirements introduction for FR2-2 |
Nokia, Nokia Shanghai Bell, Intel |
| 6.3.6.2 |
UE Demodulation and CSI requirements |
|
| R4-2218306 |
Collection of Simulation Results for UE demodulation in FR2-2 |
Ericsson |
| R4-2219838 |
Discussion on General FR2-2 UE Demodulation |
Qualcomm Incorporated |
| 6.3.6.2.1 |
PDSCH requirements |
|
| R4-2218179 |
On PDSCH demod requirements for 52.6 - 71 GHz |
Apple |
| R4-2218180 |
Draft CR for PDSCH FRCs for requirements in FR2-2 |
Apple |
| R4-2218307 |
The remaining issues of the PDSCH requirements in 52.6 – 71 GHz band |
Ericsson |
| R4-2218308 |
Simulation results for PDSCH demodulation in 52.6 – 71 GHz band |
Ericsson |
| R4-2218313 |
draft CR on PDSCH requirements for 52.6 - 71 GHz band |
Ericsson |
| R4-2219056 |
On PDSCH Requirements for ext71GHz |
Nokia, Nokia Shanghai Bell |
| R4-2219057 |
PDSCH simulation results for ext71GHz |
Nokia, Nokia Shanghai Bell |
| R4-2219502 |
Discussions on open issues on FR2-2 PDSCH requirements |
Huawei, HiSilicon |
| R4-2219503 |
Simulation results on FR2-2 PDSCH requirements |
Huawei, HiSilicon |
| R4-2219511 |
Draft CR: Introduction on FR1+FR2-2 CA PDSCH requirements |
Huawei, HiSilicon |
| R4-2219839 |
Updated Simulation Results for FR2-2 UE Demodulation PDSCH |
Qualcomm Incorporated |
| R4-2220183 |
Draft CR for PDSCH FRCs for requirements in FR2-2 |
Apple |
| R4-2220184 |
draft CR on PDSCH requirements for 52.6 - 71 GHz band |
Ericsson |
| R4-2220286 |
Draft CR: General test applicability of FR2-2 UE demodulation requirements introduction |
Qualcomm |
| R4-2220288 |
Draft CR: Introduction on FR1+FR2-2 CA PDSCH requirements |
Huawei, HiSilicon |
| 6.3.6.2.2 |
PDCCH/PBCH requirements |
|
| R4-2218181 |
On PDCCH and PBCH demod requirements for 52.6 - 71 GHz |
Apple |
| R4-2218309 |
The remaining issues for PDCCH and PBCH requirements in FR2-2 |
Ericsson |
| R4-2218310 |
Simulation results for PDCCH and PBCH demodulation in FR2-2 |
Ericsson |
| R4-2219058 |
On PDCCH and PBCH requirements for ext71GHz |
Nokia, Nokia Shanghai Bell |
| R4-2219059 |
PDCCH and PBCH simulation results for ext71GHz |
Nokia, Nokia Shanghai Bell |
| R4-2219060 |
DraftCR on PDCCH requirements for ext71GHz |
Nokia, Nokia Shanghai Bell |
| R4-2219504 |
Simulation results on FR2-2 PDCCH requirements |
Huawei, HiSilicon |
| R4-2219840 |
Updated Simulation Results for FR2-2 UE Demodulation PDCCH/PBCH |
Qualcomm Incorporated |
| R4-2220185 |
DraftCR on PDCCH requirements for ext71GHz |
Nokia, Nokia Shanghai Bell |
| 6.3.6.2.3 |
CSI reporting requirements |
|
| R4-2218182 |
On CQI reporting requirements for 52.6 - 71 GHz |
Apple |
| R4-2218183 |
Draft CR for Introducing CSI reporting requirements for 52.6 - 71 GHz |
Apple |
| R4-2218311 |
CSI reporting requirements in 52.6 – 71 GHz band |
Ericsson |
| R4-2218312 |
Simulation results for CSI reporting requirements in FR2-2 |
Ericsson |
| R4-2219061 |
On CSI reporting requirements for ext71GHz |
Nokia, Nokia Shanghai Bell |
| R4-2219062 |
CSI Simulation Results for ext71GHz |
Nokia, Nokia Shanghai Bell |
| R4-2219505 |
Discussions on open issues on FR2-2 CQI requirements |
Huawei, HiSilicon |
| R4-2219506 |
Simulation results on FR2-2 CQI requirements |
Huawei, HiSilicon |
| R4-2219842 |
Discussion on FR2-2 CQI Requirements |
Qualcomm Incorporated |
| R4-2220186 |
Draft CR for Introducing CSI reporting requirements for 52.6 - 71 GHz |
Apple |
| 6.3.6.3.1 |
PUSCH requirements |
|
| R4-2218703 |
Discussion on general and PUSCH demodulation for NR FR2-2 |
Ericsson |
| R4-2218704 |
Simulation results for NR FR2-2 PUSCH demodulation results. |
Ericsson |
| R4-2218705 |
draft CR for TS38.104 FRC table for FR2-2 PUSCH demodulation |
Ericsson |
| R4-2218706 |
draft CR for TS38.141-2 FRC table for FR2-2 PUSCH demodulation |
Ericsson |
| R4-2219014 |
Discussion and simulation results on PUSCH demodulation requirement for Rel-17 71GHz |
Samsung |
| R4-2219507 |
Discussions on open issues on FR2-2 PUSCH demodulation requirements |
Huawei, HiSilicon |
| R4-2219508 |
Simulation results on FR2-2 PUSCH demodulation requirements |
Huawei, HiSilicon |
| R4-2219512 |
Draft CR: Introduction on FR2-2 PUSCH requirements in TS 38.141-2 |
Huawei, HiSilicon |
| R4-2219729 |
Discussion on PUSCH demodulation requirements for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
| R4-2219730 |
PUSCH simulation results for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
| R4-2219731 |
Draft CR 38.104: PUSCH requirements for FR2-2 |
Nokia, Nokia Shanghai Bell, Intel |
| R4-2220174 |
draft CR for TS38.104 FRC table for FR2-2 PUSCH demodulation |
Ericsson |
| R4-2220175 |
draft CR for TS38.141-2 FRC table for FR2-2 PUSCH demodulation |
Ericsson |
| R4-2220176 |
Draft CR 38.104: PUSCH requirements for FR2-2 |
Nokia, Nokia Shanghai Bell, Intel |
| R4-2220177 |
Draft CR: Introduction on FR2-2 PUSCH requirements in TS 38.141-2 |
Huawei, HiSilicon |
| R4-2220283 |
Draft CR 38.104: PUSCH requirements for FR2-2 |
Nokia, Nokia Shanghai Bell, Intel |
| 6.3.6.3.2 |
PUCCH requirements |
|
| R4-2219015 |
Simulation results on PUCCH demodulation requirement for Rel-17 71GHz |
Samsung |
| R4-2219509 |
Simulation results on FR2-2 PUCCH demodulation requirements |
Huawei, HiSilicon |
| R4-2219513 |
Draft CR: Introduction on FR2-2 PUCCH requirements in TS 38.104 |
Huawei, HiSilicon |
| R4-2219732 |
PUCCH simulation results for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
| R4-2219733 |
Draft CR 38.141-2: PUCCH requirements for FR2-2 |
Nokia, Nokia Shanghai Bell, Intel |
| R4-2220178 |
Draft CR 38.141-2: PUCCH requirements for FR2-2 |
Nokia, Nokia Shanghai Bell, Intel |
| R4-2220179 |
Draft CR: Introduction on FR2-2 PUCCH requirements in TS 38.104 |
Huawei, HiSilicon |
| R4-2220284 |
Draft CR 38.141-2: PUCCH requirements for FR2-2 |
Nokia, Nokia Shanghai Bell, Intel |
| 6.3.6.3.3 |
PRACH requirements |
|
| R4-2219016 |
Simulation results on PRACH demodulation requirement for Rel-17 71GHz |
Samsung |
| R4-2219510 |
Simulation results on FR2-2 PRACH performance requirements |
Huawei, HiSilicon |
| R4-2219734 |
Remaining issues for PRACH demodulation requirements in FR2-2 |
Nokia, Nokia Shanghai Bell |
| R4-2219735 |
PRACH simulation results for demodulation requirements for the extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
| R4-2219736 |
Draft CR 38.104: PRACH requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
| R4-2219737 |
Draft CR 38.141-2: PRACH requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
| R4-2220180 |
Draft CR 38.104: PRACH requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
| R4-2220181 |
Draft CR 38.141-2: PRACH requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
| 6.3.7 |
Moderator summary and conclusions |
|
| R4-2220052 |
Topic summary for [105][206] NR_ext_to_71GHz_RRM_1 |
Moderator (Huawei) |
| R4-2220053 |
Topic summary for [105][207] NR_ext_to_71GHz_RRM_2 |
Moderator (Qualcomm) |
| R4-2220083 |
Topic summary for [105][103] NR_ext_to_71GHz |
Moderator (Qualcomm) |
| R4-2220132 |
Summary for [105][306] NR_exto71GHz_BSRF |
Moderator (Huawei) |
| R4-2220146 |
Summary for [105][320] NR_exto71GHz_Demod_Part1 |
Moderator (Nokia) |
| R4-2220147 |
Summary for [105][321] NR_exto71GHz_Demod_Part2 |
Moderator (Qualcomm) |
| R4-2220182 |
WF for FR2-2 BS demodulation requirements |
Nokia |
| R4-2220187 |
WF for FR2-2 UE demodulation part |
Qualcomm |
| R4-2220280 |
WF for FR2-2 MU calculation |
Huawei |
| 6.4.1 |
UE RF requirement maintenance |
|
| R4-2219803 |
CR on DMRS bundling support for CA in FR1 |
Ericsson |
| R4-2219882 |
CR for 38.101-1 DMRS bundling with FR1 uplink CA |
Qualcomm Incorporated |
| R4-2220035 |
CR to clarify UE requirements for DMRS bundling |
MediaTek (Chengdu) Inc. |
| R4-2220599 |
CR on DMRS bundling support for CA in FR1 |
Ericsson |
| R4-2220829 |
CR for 38.101-1 DMRS bundling with FR1 uplink CA |
Qualcomm Incorporated |
| 6.4.2 |
BS demodulation requirements |
|
| R4-2218058 |
Big CR for coverage enhancement performance requirements for TS38.104 |
China Telecom |
| R4-2218708 |
draft CR for TS38.141-1 manufacture declaration, applicability rule for NR coverage enhancement |
Ericsson |
| R4-2218709 |
draft CR for TS38.141-2 manufacture declaration, applicability rule for NR coverage enhancement |
Ericsson |
| R4-2218710 |
Big CR for TS38.141-1 NR coverage enhancement demodulation requirement |
Ericsson |
| R4-2219726 |
Big CR for coverage enhancement performance requirements for TS38.141-2 |
Nokia, Nokia Shanghai Bell |
| 6.4.2.1 |
PUSCH requirements |
|
| R4-2218055 |
On BS demodulation requirements for NR coverage enhancements |
China Telecom |
| R4-2218056 |
Draft CR on PUSCH with DMRS bundling BS performance test for TS 38.141-1 |
China Telecom |
| R4-2218057 |
Draft CR on PUSCH with DMRS bundling BS performance test for TS 38.141-2 |
China Telecom |
| R4-2218707 |
draft CR for TS38.104 PUSCH with JCE demodulation requirements for FR1 and FR2 |
Ericsson |
| R4-2219652 |
Draft CR on requirements for PUSCH TBoMS (TS38.104, Rel-17) |
Huawei, HiSilicon |
| R4-2219653 |
Draft CR on requirements for PUSCH TBoMS (TS38.141-1, Rel-17) |
Huawei, HiSilicon |
| R4-2219654 |
Draft CR on requirements for PUSCH TBoMS (TS38.141-2, Rel-17) |
Huawei, HiSilicon |
| R4-2219656 |
Simulation results on BS coverage enhancement demod PUSCH |
Huawei, HiSilicon |
| R4-2219686 |
Summary of simulation results for PUSCH coverage enhancements |
China Telecom |
| R4-2220188 |
Draft CR on requirements for PUSCH TBoMS (TS38.104, Rel-17) |
Huawei, HiSilicon |
| R4-2220189 |
Draft CR on requirements for PUSCH TBoMS (TS38.141-1, Rel-17) |
Huawei, HiSilicon |
| R4-2220190 |
Draft CR on requirements for PUSCH TBoMS (TS38.141-2, Rel-17) |
Huawei, HiSilicon |
| 6.4.2.2 |
PUCCH requirements |
|
| R4-2219012 |
Simulation results for PUCCH demodulation requirement for Rel-17 coverage enhancement |
Samsung |
| R4-2219013 |
Draft CR on PUCCH JCE requirements for TS 38.104 |
Samsung |
| R4-2219655 |
Simulation results on BS coverage enhancement demod PUCCH |
Huawei, HiSilicon |
| R4-2219724 |
Draft CR for 38.141-1: Perf requirements for PUCCH JCE |
Nokia, Nokia Shanghai Bell |
| R4-2219725 |
Draft CR for 38.141-2: Perf requirements for PUCCH JCE |
Nokia, Nokia Shanghai Bell |
| R4-2219727 |
Simulation results collection for coverage enhancement for PUCCH |
Nokia, Nokia Shanghai Bell |
| R4-2220191 |
Draft CR on PUCCH JCE requirements for TS 38.104 |
Samsung |
| R4-2220192 |
Draft CR for 38.141-1: Perf requirements for PUCCH JCE |
Nokia, Nokia Shanghai Bell |
| R4-2220193 |
Draft CR for 38.141-2: Perf requirements for PUCCH JCE |
Nokia, Nokia Shanghai Bell |
| 6.4.3 |
Moderator summary and conclusions |
|
| R4-2220084 |
Topic summary for [105][104] NR_cov_enh_maintenance |
Moderator (China Telecom) |
| R4-2220148 |
Summary for [105][322] NR_cov_enh_Demod |
Moderator (China Telecom) |
| 6.5.1 |
RRM core requirement maintenance |
|
| R4-2218184 |
On Remaining Issues for FeMIMO RRM Core Requirements |
Apple |
| R4-2218185 |
CR for Unified TCI State switching requirements |
Apple |
| R4-2218186 |
CR for Inter-cell Beam Management |
Apple |
| R4-2218331 |
Discussion on remaining issue in Rel-17 FeMIMO |
Intel Corporation |
| R4-2218744 |
Discussion on R17 feMIMO for RRM core requirement maintenance |
MediaTek Inc. |
| R4-2218935 |
Remaining issues for UL TCI state switch |
Nokia, Nokia Shanghai Bell |
| R4-2219027 |
Discussion on remaining issues of FeMIMO RRM core requirements |
Samsung |
| R4-2219172 |
Discussion on remaining issues in R17 feMIMO RRM requirements |
vivo |
| R4-2219173 |
CR on R17 feMIMO RRM requirements |
vivo |
| R4-2219245 |
Discussion on RRM core remaining issues for R17 FeMIMO |
Huawei, HiSilicon |
| R4-2219246 |
CR on maintaining RRM requirements for R17 FeMIMO |
Huawei, HiSilicon |
| R4-2219437 |
Discussion on remaining RRM requirements for FeMIMO |
ZTE Corporation |
| R4-2219691 |
CR on conditions for PL-RS maintenance |
Nokia, Nokia Shanghai Bell |
| R4-2219943 |
Discussion on remanining open issue of FeMIMO |
Ericsson |
| R4-2219944 |
CR on maintenance of FeMIMO |
Ericsson |
| R4-2220405 |
CR for Unified TCI State switching requirements |
Apple |
| R4-2220406 |
CR for Inter-cell Beam Management |
Apple |
| R4-2220407 |
CR on R17 feMIMO RRM requirements |
vivo |
| R4-2220408 |
CR on maintaining RRM requirements for R17 FeMIMO |
Huawei, HiSilicon |
| R4-2220409 |
CR on conditions for PL-RS maintenance |
Nokia, Nokia Shanghai Bell |
| R4-2220410 |
CR on maintenance of FeMIMO |
Ericsson |
| R4-2220712 |
CR on R17 feMIMO RRM requirements |
vivo |
| 6.5.2 |
RRM performance requirements |
|
| R4-2218187 |
On Remaining Issues for FeMIMO Performance Requirements |
Apple |
| R4-2219032 |
Big CR for NR feMIMO RRM performance requirements |
Samsung |
| R4-2219247 |
Discussion on remaining issues for R17 FeMIMO test cases |
Huawei, HiSilicon |
| R4-2220311 |
WF on Rel-17 FeMIMO RRM performance requirements |
Samsung |
| R4-2220312 |
WF on Rel-17 FeMIMO RRM core requirement maintenance |
Intel Corporation |
| R4-2220713 |
WF on Rel-17 FeMIMO RRM core requirement maintenance |
Intel Corporation |
| 6.5.2.1 |
General (test configurations, side condition and etc) |
|
| R4-2219174 |
Discussion on general aspects for R17 feMIMO Test cases |
vivo |
| R4-2219175 |
Draft CR on general configurations in R17 feMIMO test cases |
vivo |
| R4-2219945 |
on general configuration |
Ericsson |
| R4-2220436 |
Draft CR on general configurations in R17 feMIMO test cases |
vivo |
| 6.5.2.2 |
Test cases for unified TCI state switching |
|
| R4-2218745 |
Draft CR on TC for joint unified TCI state switching in FR2 NR SA |
MediaTek Inc. |
| R4-2219028 |
Discussion on remaining issues of test cases for unified TCI state |
Samsung |
| R4-2219030 |
CR on test cases of Unified TCI state switch delay |
Samsung |
| R4-2219176 |
draft CR on test cases for R17 unified TCI |
vivo |
| R4-2219248 |
CR on maintaining unified TCI state switching test cases |
Huawei, HiSilicon |
| R4-2220308 |
CR on test cases of Unified TCI state switch delay |
Samsung |
| R4-2220309 |
draft CR on test cases for R17 unified TCI |
vivo |
| R4-2220428 |
Draft CR on TC for joint unified TCI state switching in FR2 NR SA |
MediaTek Inc. |
| 6.5.2.4 |
Test cases for TRP specific BFD and LR |
|
| R4-2218188 |
Draft CR for correcting TRP specific BFR test cases |
Apple |
| R4-2219029 |
Discussion on remaining issues of test cases for TRP specific BFD and LR |
Samsung |
| R4-2219031 |
CR on test cases of TRP specific BFR |
Samsung |
| R4-2219249 |
CR on maintaining CSI-RS configuration used for TRP specific BFR test cases |
Huawei, HiSilicon |
| R4-2220310 |
Draft CR for correcting TRP specific BFR test cases |
Apple |
| 6.5.3 |
UE Demodulation and CSI requirements |
|
| R4-2218931 |
Simulation results summary for FeMIMO demodulation and CSI requirement |
Samsung |
| R4-2219024 |
Big CR on UE demodulation and CSI requirement for FeMIMO |
Samsung |
| 6.5.3.1.1 |
Enhancement on HST-SFN scenario |
|
| R4-2218189 |
Simulation results for demod requirements with HST-SFN Scheme-A |
Apple |
| R4-2218190 |
Draft CR on PDSCH requirement for HST-SFN scheme A |
Apple |
| R4-2219276 |
Update simulation restuls for PDSCH requirement for HST-SFN |
Ericsson |
| R4-2219657 |
Draft CR on PDSCH requirement for HST-SFN scheme B |
Huawei, HiSilicon |
| R4-2219658 |
Simulation results on UE FeMIMO demod HST-SFN |
Huawei, HiSilicon |
| R4-2220194 |
Draft CR on PDSCH requirement for HST-SFN scheme A |
Apple |
| R4-2220195 |
Draft CR on PDSCH requirement for HST-SFN scheme B |
Huawei, HiSilicon |
| 6.5.3.1.2 |
Enhancement on Multi-TRP |
|
| R4-2219277 |
draft CR to 38.101-4: PDCCH requirement for enhancement on multi-TRP |
Ericsson |
| R4-2219659 |
Simulation results on UE FeMIMO demod mTRP |
Huawei, HiSilicon |
| R4-2219960 |
CR on reference measurement channels for multi-TRP PDCCH performance |
Qualcomm Incorporated |
| 6.5.3.2 |
CSI requirements |
|
| R4-2218371 |
Simulation Results on PMI Reporting Requirement for m-TRP CSI |
Qualcomm Incorporated |
| 6.5.4 |
Moderator summary and conclusions |
|
| R4-2220054 |
Topic summary for 105][208] NR_feMIMO_RRM_1 |
Moderator (Intel) |
| R4-2220055 |
Topic summary for [105][209] NR_feMIMO_RRM_2 |
Moderator (Samsung) |
| R4-2220149 |
Summary for [105][323] NR_FeMIMO_Demod |
Moderator (Samsung) |
| 6.6.2 |
RRM core requirement maintenance |
|
| R4-2218137 |
On remaining issues of RRM requirement for RedCap UE |
Apple |
| R4-2218138 |
LS on reference SSB for s-MeasureConfig checking |
Apple |
| R4-2218139 |
CR on CG-SDT with RedCap eDRX R17 |
Apple |
| R4-2218576 |
Discussion on remaining issues for RRM core requirement maintenance for Redcap UE |
Xiaomi |
| R4-2218602 |
Discussions on RedCap mobility requirements |
ZTE Corporation |
| R4-2218624 |
On remaining issues for RedCap core requirements |
CMCC |
| R4-2218798 |
Consideration on maintenance issues for Redcap |
vivo |
| R4-2218936 |
CR on corrections to RedCap Core requirements |
Nokia, Nokia Shanghai Bell |
| R4-2219320 |
Discussions on RedCap HO |
Ericsson |
| R4-2219321 |
CR on RedCap HO |
Ericsson, Huawei, HiSilicon |
| R4-2219392 |
Discussion on remaining issues in handover for RedCap |
Huawei, HiSilicon |
| R4-2219393 |
Correction on measurement requirements for RedCap UE |
Huawei, HiSilicon |
| R4-2219770 |
RRM core requirement maintenance |
Nokia, Nokia Shanghai Bell |
| R4-2219935 |
Discussion on mobility requirements |
MediaTek inc. |
| R4-2219936 |
CR on RedCap maintenance in TS 38.133 |
MediaTek inc. |
| R4-2220029 |
Remaining issues for RedCap RRM |
Qualcomm Incorporated |
| R4-2220039 |
CR on measurement procedures for RedCap UEs |
Qualcomm Incorporated |
| R4-2220040 |
CR on timing requirements with measurement gaps for RedCap UEs |
Qualcomm Incorporated |
| R4-2220041 |
CR on RRC Connection mobility control |
Qualcomm Incorporated |
| R4-2220323 |
CR on measurement procedures for RedCap UEs |
Qualcomm Incorporated |
| R4-2220324 |
CR on RRC Connection mobility control |
Qualcomm Incorporated |
| R4-2220431 |
CR on CG-SDT with RedCap eDRX R17 |
Apple |
| R4-2220432 |
CR on corrections to RedCap Core requirements |
Nokia, Nokia Shanghai Bell |
| R4-2220433 |
CR on RedCap HO |
Ericsson, Huawei, HiSilicon |
| R4-2220434 |
CR on timing requirements with measurement gaps for RedCap UEs |
Qualcomm Incorporated |
| 6.6.3 |
RRM performance requirements |
|
| R4-2219829 |
Updated test case list for RedCap RRM performance part |
Ericsson |
| R4-2219830 |
Big CR for Performance part of RedCap - TS 38.133 |
Ericsson |
| R4-2219831 |
Correction to CONNECTED mode measurement requirements for eMTC over NTN |
Ericsson |
| R4-2220322 |
WF on Rel-17 NR RedCap RRM Core requirement maintenance |
Vivo |
| R4-2220325 |
WF on Rel-17 NR RedCap RRM Performance requirements |
Ericsson |
| R4-2220714 |
WF on Rel-17 NR RedCap RRM Core requirement maintenance |
Vivo |
| 6.6.3.1 |
General (test configurations, side condition and etc) |
|
| R4-2218339 |
Discussion on CG-SDT test cases of RedCap UE |
Intel Corporation |
| R4-2218975 |
Discussion on NCD-SSB tests for RedCap UEs |
OPPO |
| R4-2219322 |
Discussions on RedCap NCD-SSB test design |
Ericsson, CATT |
| R4-2219323 |
draftCR on RedCap NCD-SSB RMC |
Ericsson |
| 6.6.3.2 |
RRM test cases for FR1 |
|
| R4-2218340 |
DraftCR on CG-SDT test cases in FR1 for RedCap UE |
Intel Corporation |
| R4-2218474 |
Draft CR on SA event triggered reporting tests with per-UE gaps under non-DRX for RedCap UE in FR1 |
CATT |
| R4-2218625 |
Draft CR on test case for FR1 active BWP swith and UE specific CBW change |
CMCC |
| R4-2218937 |
draft CR on corrections to RRM test cases for FR1 |
Nokia, Nokia Shanghai Bell |
| R4-2218976 |
CR on SA test for intra-frequency measurement with per-UE gaps under non-DRX with SSB index reading |
OPPO |
| R4-2219394 |
Correction to FR1 RedCap test cases |
Huawei, HiSilicon |
| R4-2220326 |
DraftCR on CG-SDT test cases in FR1 for RedCap UE |
Intel Corporation |
| R4-2220327 |
CR on SA test for intra-frequency measurement with per-UE gaps under non-DRX with SSB index reading |
OPPO |
| R4-2220387 |
Correction to FR1 RedCap test cases |
Huawei, HiSilicon |
| 6.6.3.3 |
RRM test cases for FR2 |
|
| R4-2218341 |
DraftCR on CG-SDT test cases in FR2 for RedCap UE |
Intel Corporation |
| R4-2218626 |
Draft CR on test case for FR2 active BWP swith, UE specific CBW change, active TCI state switch and uplink spatial relation switch delay |
CMCC |
| R4-2219395 |
Correction to FR2 RedCap test cases |
Huawei, HiSilicon |
| R4-2220328 |
DraftCR on CG-SDT test cases in FR2 for RedCap UE |
Intel Corporation |
| R4-2220388 |
Correction to FR2 RedCap test cases |
Huawei, HiSilicon |
| 6.6.4 |
UE demodulation and CSI requirements |
|
| R4-2219116 |
Summary of simulation results for RedCap |
Ericsson |
| R4-2219117 |
Big CR to 38.101-4: Correction of RedCap UE demodulation and CSI reporting requirements |
Ericsson |
| 6.6.4.1.1 |
PDSCH/SDR requirements |
|
| R4-2219118 |
Draft CR: Correction of RedCap UE demodulation and CSI reporting requirements |
Ericsson |
| R4-2219841 |
draftCR for corrections to R4-2217430 BigDraftCR for RedCap UE demod |
Qualcomm Incorporated |
| 6.6.4.2 |
CSI requirements |
|
| R4-2218246 |
Draft CR to TS38.101-4, Correction to 4x1 MIMO correlation matrix |
MediaTek inc. |
| R4-2218247 |
Draft CR to TS38.101-4, Corrections to RedCap CSI requirements |
MediaTek inc. |
| 6.6.4.2.1 |
CQI requirements |
|
| R4-2219912 |
Simulation results for RedCap CQI reporting |
Nokia, Nokia Shanghai Bell |
| 6.6.5 |
Moderator summary and conclusions |
|
| R4-2220056 |
Topic summary for [105][210] NR_redcap_RRM_2 |
Moderator (US Cellular) |
| R4-2220057 |
Topic summary for [105][211] NR_redcap_RRM_1 |
Moderator (Vivo) |
| R4-2220085 |
Topic summary for [105][105] NR_RedCap |
Moderator (Ericsson) |
| R4-2220150 |
Summary for [105][324] NR_RedCap_Demod |
Moderator (Ericsson) |
| 6.7.1 |
RRM core requirement maintenance |
|
| R4-2218509 |
Open issues in core requirements for RTT-based propagation delay compensation |
Qualcomm Incorporated |
| R4-2218783 |
Remaining issues for PDC enhancement |
vivo |
| R4-2218784 |
CR to TS 38.133 Correction to measurements core requirements for PDC |
vivo,Nokia, Huawei, HiSilicon |
| R4-2219050 |
Discussion on remaining issues for NR_IIOT_URLL |
Nokia, Nokia Shanghai Bell |
| R4-2219051 |
CR to TS 38.133: Correction to measurement core requirements for PDC |
Nokia, Nokia Shanghai Bell |
| R4-2219329 |
PDC RS and MG |
Ericsson |
| R4-2219330 |
Requirements for DRX case |
Ericsson |
| R4-2219542 |
On RRM requirements for PDC enhancements |
Huawei, HiSilicon |
| R4-2219543 |
CR on requirements for UE Rx-Tx measurement for PDC |
Huawei, HiSilicon |
| R4-2220341 |
CR to TS 38.133 Correction to measurements core requirements for PDC |
vivo,Nokia, Huawei, HiSilicon |
| R4-2220737 |
CR to TS 38.133 Correction to measurements core requirements for PDC |
vivo,Nokia, Huawei, HiSilicon |
| 6.7.2 |
RRM performance requirements |
|
| R4-2218510 |
On performance requirements for RTT-based propagation delay compensation |
Qualcomm Incorporated |
| R4-2219052 |
Discussion on remaining issues for NR_IIOT_URLLC performance requirements |
Nokia, Nokia Shanghai Bell |
| R4-2219053 |
Simulation Results for TRS measurement Accuracy |
Nokia, Nokia Shanghai Bell |
| R4-2219054 |
Draft CR on UE Rx-Tx time difference measurement accuracy requirements for RTT-based PDC |
Nokia, Nokia Shanghai Bell |
| R4-2219055 |
BigCR to 38.133: measurement accuracy requirements for RTT-based PDC |
Nokia, Nokia Shanghai Bell |
| R4-2219544 |
On measurement accuracy for PDC enhancements |
Huawei, HiSilicon |
| R4-2219545 |
draftCR to on PDC measurement accuracy requirements |
Huawei, HiSilicon |
| R4-2220340 |
WF on NR Enhanced IIoT and URLLC RRM requirements |
Nokia |
| R4-2220342 |
draftCR to on PDC measurement accuracy requirements |
Huawei, HiSilicon |
| R4-2220715 |
draftCR to on PDC measurement accuracy requirements |
Huawei, HiSilicon |
| 6.7.3 |
Demodulation performance and CSI requirements |
|
| R4-2218721 |
Big CR for TS38.141-1 URLLC and IIoT reqirements |
Ericsson |
| 6.7.3.1 |
PUCCH requirements |
|
| R4-2218720 |
draft CR for TS38.141-1 PUCCH sub-slot repetition demodulation requirements |
Ericsson |
| R4-2219020 |
Simulation results for Enhanced IIOT and URLLC support |
Samsung |
| R4-2219021 |
Big CR for TS 38.141-2 Demodulation requirements for Enhanced IIOT and URLLC support |
Samsung |
| R4-2219022 |
Draft CR on OTA performance requirements for PUCCH for TS 38.141-2 |
Samsung |
| R4-2219501 |
Simulation summary for sub-slot repetition PF0 requirements |
Huawei, HiSilicon |
| R4-2219694 |
Updated Simulation Results on Sub-slot based PUCCH repetition |
Nokia, Nokia Shanghai Bell |
| R4-2219695 |
Draft CR for TS 38.104 Demod performance requirement for sub-slot repetition PUCCH format 0 (Rel-17, CAT B) |
Nokia, Nokia Shanghai Bell |
| R4-2219696 |
Big CR for TS 38.104 Demodulation requirements for Enhanced IIOT and URLLC support (Rel-17, CAT B) |
Nokia, Nokia Shanghai Bell |
| R4-2220196 |
draft CR for TS38.141-1 PUCCH sub-slot repetition demodulation requirements |
Ericsson |
| R4-2220197 |
Draft CR on OTA performance requirements for PUCCH for TS 38.141-2 |
Samsung |
| 6.7.4 |
Moderator summary and conclusions |
|
| R4-2220058 |
Topic summary for [105][212] NR_IIOT_URLLC_enh |
Moderator (Nokia) |
| R4-2220151 |
Summary for [105][325] NR_IIOT_URLLC_enh_Demod |
Moderator (Nokia) |
| 6.8.2 |
RRM performance requirements |
|
| R4-2218538 |
Draft CR for CG-SDT testcase for FR1 revision from R4-2217245 |
Qualcomm Incorporated |
| R4-2218539 |
CG-SDT performance requirements for FR1 |
Qualcomm Incorporated |
| R4-2219441 |
Discussion on RRM performance requirements for NR SDT in INACTIVE |
ZTE Corporation |
| R4-2219546 |
Discussion on RRM test cases for SDT |
Huawei, HiSilicon |
| R4-2219547 |
draftCR on SDT RRM test case for FR2 |
Huawei, HiSilicon |
| R4-2219918 |
Discussion on RRM performance requirements for SDT |
MediaTek inc. |
| R4-2220343 |
WF on NR SDT in INACTIVE state RRM requirements |
MediaTek |
| R4-2220344 |
Draft CR for CG-SDT testcase for FR1 revision from R4-2217245 |
Qualcomm Incorporated |
| R4-2220345 |
draftCR on SDT RRM test case for FR2 |
Huawei, HiSilicon |
| R4-2220414 |
Big CR for NR small data transmissions in INACTIVE state RRM performance requirements |
ZTE |
| R4-2220716 |
Draft CR for CG-SDT testcase for FR1 revision from R4-2217245 |
Qualcomm Incorporated |
| 6.8.3 |
Moderator summary and conclusions |
|
| R4-2219738 |
Discussion on performance requirements for SDT |
Nokia, Nokia Shanghai Bell |
| R4-2220059 |
Topic summary for [105][213] NR_SmallData_INACTIVE |
Moderator (MediaTek) |
| 7.1.1 |
UE RF requirements |
|
| R4-2218112 |
Sub-1GHz band pairing with UL CA_n77(2A) and CA_n78(2A) |
Apple |
| R4-2218622 |
Unified Triple Beat Detection Equations for all 4 Triple Beats |
Murata Manufacturing Co Ltd. |
| 7.1.1.1 |
band combinations with UL configurations including intra-band ULCA with IMD or triple beat issues |
|
| R4-2218125 |
DC_3C_n26A Triple Beat MSD Update |
Murata Manufacturing Co Ltd. |
| R4-2218126 |
Triple Beat MSD in 3rd DL Band for DC_3C-1A_n75A and DC_3C-7A_n26A |
Murata Manufacturing Co Ltd. |
| R4-2218518 |
Handling spectrum restrictions and specifying MSD due to IMDs of intra-band ULCA in inter-band combinations |
Skyworks Solutions Inc. |
| R4-2218519 |
DraftCR to 38.101-1 on correcting REFSENS exceptions due to intermodulation interference of intra-band ULCA |
Skyworks Solutions Inc. |
| R4-2218760 |
Draft CR for 38.101-1 to add missing configurations and intoduce new configurations for NR inter-band CA 3 bands |
Samsung, Telus, Bell Mobility |
| R4-2218761 |
Draft CR for 38.101-1 to introduce new configurations for NR inter-band CA 4 bands |
Samsung, Telus, Bell Mobility |
| R4-2219085 |
TP to TR 38.718-02-01 Addition of CA_n5-n77 |
Nokia, Bell, Telus |
| R4-2219086 |
TP to TR 38.718-02-01 Addition of CA_n7-n77 |
Nokia, Bell, Telus |
| R4-2219087 |
TP to TR 38.718-02-01 Addition of CA_n25-n77 |
Nokia, Bell, Telus |
| R4-2219088 |
TP to TR 38.718-02-01 Addition of CA_n66-n77 |
Nokia, Bell, Telus |
| R4-2219089 |
TP to TR 38.718-02-01 Addition of CA_n71-n77 |
Nokia, Bell, Telus |
| R4-2219090 |
TP to TR 38.718-03-01 Addition of CA_n5-n7-n77 |
Nokia, Bell, Telus |
| R4-2219091 |
TP to TR 38.718-03-01 Addition of CA_n7-n71-n77 |
Nokia, Bell, Telus |
| R4-2219092 |
Draft CR to 38.101-1 CA_n5A-n7A-n77(3A) configuration |
Nokia, Bell, Telus |
| R4-2219093 |
Draft CR to 38.101-1 CA_n5A-n25A-n77(3A) configuration |
Nokia, Bell, Telus |
| R4-2219094 |
Draft CR to 38.101-1 CA_n5A-n66A-n77(3A) configuration |
Nokia, Bell, Telus |
| R4-2219095 |
Draft CR to 38.101-1 CA_n7A-n25A-n77(3A) configuration |
Nokia, Bell, Telus |
| R4-2219096 |
Draft CR to 38.101-1 CA_n7A-n66A-n77(3A) configuration |
Nokia, Bell, Telus |
| R4-2219097 |
Draft CR to 38.101-1 CA_n7A-n71A-n77(3A) configuration |
Nokia, Bell, Telus |
| R4-2219098 |
Draft CR to 38.101-1 CA_n25A-n66A-n77(3A) configuration |
Nokia, Bell, Telus |
| R4-2219099 |
Draft CR to 38.101-1 CA_n25-n71-n77 configurations |
Nokia, Bell, Telus |
| R4-2219100 |
Draft CR to 38.101-1 CA_n66A-n71A-n77(3A) configuration |
Nokia, Bell, Telus |
| R4-2219303 |
TP for TR 37.718-11-11 to include updates for DC_3_n26 |
Ericsson, Skyworks, Telstra |
| R4-2219304 |
TP for TR 37.718-11-11 to include updates for DC_7_n26 |
Ericsson, Skyworks, Telstra |
| R4-2219305 |
TP for TR 37.718-11-11 to include updates for DC_3-7_n26 |
Ericsson, Skyworks, Telstra |
| R4-2219700 |
Triple-beat MSD for DC_3C_n26A and DC_3-7_n26 |
Skyworks Solutions Inc. |
| R4-2219701 |
Triple beat MSD for DC_3C_n1A-n75A and DC_3C-32A_n1A |
Skyworks Solutions Inc. |
| R4-2219702 |
Missing Triple beat MSD and Updates on Detection Criteria |
Skyworks Solutions Inc. |
| R4-2220554 |
Ad hoc minutes for NR_Baskets_Part_1 |
Skyworks |
| R4-2220555 |
WF on frequency restrictions and MSD test points definition for inter-band combinations with intra-band UCLA configuration |
Skyworks, Mediatek |
| R4-2220556 |
WF on triple beat rules and related MSD test points definition for inter-band combinations with 2UL with intra-band UCLA configuration |
Murata, Skyworks |
| R4-2220557 |
Draft CR to capture triple beat MSD requirements |
Skyworks, Murata |
| R4-2220558 |
WF on missing Scell MSD for intra-band contiguous ENDC |
Skyworks Solutions Inc. |
| R4-2220559 |
Draft CR to capture MSD to Scell for intra-band contiguous ENDC |
Skyworks Solutions Inc. |
| R4-2220560 |
WF on 1UL CA_n71-n85 architecture and requirement |
T-Mobile USA |
| R4-2220561 |
DraftCR to 38.101-1 on correcting REFSENS exceptions due to intermodulation interference of intra-band ULCA |
Skyworks Solutions Inc. |
| R4-2220562 |
TP to TR 38.718-02-01 Addition of CA_n25-n77 |
Nokia, Bell, Telus |
| R4-2220563 |
TP to TR 38.718-02-01 Addition of CA_n66-n77 |
Nokia, Bell, Telus |
| R4-2220566 |
TP for TR 37.718-11-11 to include updates for DC_3_n26 |
Ericsson, Skyworks, Telstra |
| R4-2220567 |
TP for TR 37.718-11-11 to include updates for DC_7_n26 |
Ericsson, Skyworks, Telstra |
| R4-2220568 |
TP for TR 37.718-11-11 to include updates for DC_3-7_n26 |
Ericsson, Skyworks, Telstra |
| 7.1.1.2 |
Others |
|
| R4-2218967 |
TP for TR 38.718-02-01 to update CA_n7-n26 |
Ericsson, Skyworks, Telstra |
| R4-2219273 |
DraftCR add uplink CA_n78(2A) to the existing two bands DL CA combinations |
Huawei, HiSilicon, BT |
| R4-2219476 |
On spectrum restrictions in MSD analysis |
Qualcomm Inc. |
| R4-2219703 |
Missing Three-band MSD to Scell for intra-band contiguous with IMD |
Skyworks Solutions Inc. |
| R4-2220569 |
TP for TR 38.718-02-01 to update CA_n7-n26 |
Ericsson, Skyworks, Telstra |
| 7.1.2 |
Moderator summary and conclusions |
|
| R4-2220086 |
Topic summary for [105][106] NR_Baskets_Part_1 |
Moderator (Skyworks) |
| 7.2 |
Moderator summary and conclusions (for basket WI AI 7.3 to AI 7.26 ) |
|
| R4-2220087 |
Topic summary for [105][107] NR_Baskets_Part_2 |
Moderator (Nokia) |
| R4-2220088 |
Topic summary for [105][108] NR_Baskets_Part_3 |
Moderator (Ericsson) |
| R4-2220089 |
Topic summary for [105][109] NR_Baskets_Part_4 |
Moderator (Nokia) |
| R4-2220091 |
Topic summary for [105][111] NR_LTE_V2X_PC5_combos |
Moderator (CATT) |
| R4-2220092 |
Topic summary for [105][112] LTE_NR_HPUE_FWVM |
Moderator (Nokia) |
| R4-2220093 |
Topic summary for 105][113] HPUE_Basket_EN-DC |
Moderator (Ericsson) |
| R4-2220094 |
Topic summary for [105][114] HPUE_Basket_Intra-CA_TDD |
Moderator (Hisilicon) |
| R4-2220095 |
Topic summary for [105][115] HPUE_Basket_inter-CA_SUL |
Moderator (China Telecom) |
| R4-2220096 |
Topic summary for [105][116] HPUE_Basket_FDD |
Moderator (China Unicom) |
| R4-2220097 |
Topic summary for [105][117] LTE_NR_Other_WI |
Moderator (Huawei) |
| 7.3.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218550 |
TR 37.718-11-11 v0.3.0 Rel-18 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
| R4-2218551 |
Big CR for Rel-18 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
| R4-2218552 |
Revised WID for Rel-18 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
| 7.3.2 |
UE RF requirements without FR2 band |
|
| R4-2218521 |
Draft CR for TS 38.101-3: Support of n78(A-C) in DC_1_n78, DC_3_n78, DC_5_n78, DC_7_n78 and DC_7-7_n78 |
SK Telecom |
| R4-2218957 |
TP for 37.718-11-11 to include DC_28_n38 |
Ericsson |
| R4-2219101 |
TP to TR 37.718-11-11 Addition of DC_8_n38 |
Nokia, Telefonica |
| R4-2219756 |
Draft CR for TS 38.101-3 to update delta TIB template for NE-DC combinations |
ZTE Corporation |
| R4-2219758 |
TP for TR 37.718-11-11 on delta TIB and RIB templates for NE-DC combinations |
ZTE Corporation |
| R4-2220606 |
Draft CR for TS 38.101-3: Support of n78(A-C) in DC_1_n78, DC_3_n78, DC_5_n78, DC_7_n78 and DC_7-7_n78 |
SK Telecom |
| R4-2220763 |
TP for 37.718-11-11 to include DC_28_n38 |
Ericsson |
| R4-2220767 |
TP to TR 37.718-11-11 Addition of DC_8_n38 |
Nokia, Telefonica |
| 7.3.3 |
UE RF requirements with FR2 band |
|
| R4-2218919 |
Draft CR 38.101-3 to add DC_26A_n258A/B/C/D/E/F/G/H/I/J/K/L/M |
Ericsson, Telstra |
| 7.4.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2219165 |
TR 37.718-21-11 V0.3.0 for DC of 2 LTE band and 1 NR band |
Huawei, HiSilicon |
| R4-2219166 |
CR on introduction of completed DC of 2 bands LTE and 1 band NR into TS 38.101-3 |
Huawei, HiSilicon |
| R4-2219167 |
Rel-18 WID: Dual Connectivity (DC) of 2 bands LTE inter-band CA (2DL/1UL) and 1 NR band (1DL/1UL) |
Huawei, HiSilicon |
| 7.4.2 |
UE RF requirements without FR2 band |
|
| R4-2218522 |
Draft CR for TS 38.101-3: Support of n78(A-C) in DC_1-3_n78, DC_1-5_n78, DC_1-7_n78, DC_3-5_n78, DC_3-7_n78, DC_5-7_n78, DC_1-7-7_n78, DC_3-7-7_n78 and DC_5-7-7_n78 |
SK Telecom |
| R4-2218524 |
TP for TR 37.718-21-11 DC_1A-5A_n40A |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2218525 |
TP for TR 37.718-21-11 DC_3A-5A_n40A |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2218958 |
TP for 37.718-21-11 to include DC_1-28_n38 |
Ericsson |
| R4-2218959 |
TP for 37.718-21-11 to include DC_3-28_n38 |
Ericsson |
| R4-2218960 |
TP for 37.718-21-11 to include DC_7-28_n38 |
Ericsson |
| R4-2219282 |
TP for TR 37.718-21-11: DC_20-28_n78 |
Vodafone Ireland Plc |
| R4-2219338 |
TP for TR 37.718-21-11: DC_1-28_n20 |
Vodafone Ireland Plc |
| R4-2219424 |
TP for TR 37.718-21-11: DC_1-3_n1 |
Vodafone Ireland Plc, MediaTek |
| R4-2219426 |
TP for TR 37.718-21-11: DC_1-20_n1 |
Vodafone Ireland Plc, MediaTek |
| R4-2219448 |
TP for TR 37.718-21-11: DC_7-8_n20 |
Vodafone Ireland Plc, MediaTek |
| R4-2219462 |
TP for TR 37.718-21-11: DC_7-28_n20 |
Vodafone Ireland Plc |
| R4-2220607 |
TP for TR 37.718-21-11 DC_1A-5A_n40A |
SK Telecom, Murata Manufacturing Co. Ltd |
| R4-2220773 |
TP for TR 37.718-21-11: DC_1-3_n1 |
Vodafone Ireland Plc, MediaTek |
| R4-2220774 |
TP for TR 37.718-21-11: DC_1-20_n1 |
Vodafone Ireland Plc, MediaTek |
| R4-2220775 |
TP for TR 37.718-21-11: DC_7-8_n20 |
Vodafone Ireland Plc, MediaTek |
| R4-2220776 |
TP for TR 37.718-21-11: DC_7-28_n20 |
Vodafone Ireland Plc |
| 7.4.3 |
UE RF requirements with FR2 band |
|
| R4-2218918 |
Draft CR 38.101-3 to add DC_1A/3A/7A-26A_n258A/B/C/D/E/F/G/H/I/J/K/L/M |
Ericsson, Telstra |
| 7.5.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2219077 |
Revised Rel-18 WID on DC of x bands LTE inter-band CA (x=3,4,5) and 1 NR band |
Nokia, Nokia Shanghai Bell |
| R4-2219078 |
draft Big CR to introduce new combinations DC of x bands LTE inter-band CA (x345) and 1 NR band |
Nokia, Nokia Shanghai Bell |
| R4-2219079 |
Big CR to introduce new combinations DC of x bands LTE inter-band CA (x345) and 1 NR band |
Nokia, Nokia Shanghai Bell |
| 7.5.2 |
UE RF requirements without FR2 band |
|
| R4-2218380 |
Draft CR for 38.101-3 to add DC_3C-7A-20A-38A_n78A |
Huawei, Hisilicon |
| R4-2218384 |
Draft CR for 38.101-3 to add DC_3A-7A-32A_n1A-n78A |
Huawei, Hisilicon |
| R4-2218523 |
Draft CR for TS 38.101-3: Support of n78(A-C) in DC_1-3-5_n78, DC_1-3-7_n78, DC_1-5-7_n78, DC_3-5-7_n78, DC_1-3-7-7_n78, DC_1-5-7-7_n78, DC_3-5-7-7_n78, DC_1-3-5-7_n78 and DC_1-3-5-7-7_n78 |
SK Telecom |
| R4-2218916 |
Draft CR 38.101-3 to add DC_1A-3A-7C-26A_n78(2A) and fall backs |
Ericsson, Telstra |
| R4-2218917 |
Draft CR 38.101-3 to add DC_1A-3A-7C-28A_n78(2A) and fall backs |
Ericsson, Telstra |
| R4-2218930 |
draft CR for DC_3A-7A-8B_n78A, DC_3A-3A-7A-8B_n78A, DC_3A-7A-7A-8B_n78A, DC_3A-3A-7A-7A-8B_n78A |
CHTTL |
| R4-2218962 |
draft CR 38.101-3 to include new combinations with band n78 |
Ericsson |
| R4-2218963 |
draft CR 38.101-3 to include new combinations with band n1 |
Ericsson |
| R4-2218964 |
draft CR 38.101-3 to include new EN-DC combinations with band n38 |
Ericsson |
| R4-2219292 |
Draft CR 38.101-3 to add DC_1A-3A-7A_n1A |
Vodafone Ireland Plc |
| R4-2219306 |
Draft CR 38.101-3 to add DC_1A-3A-20A_n1A |
Vodafone Ireland Plc |
| R4-2219307 |
Draft CR 38.101-3 to add DC_1A-7A-8A_n20A |
Vodafone Ireland Plc |
| R4-2219335 |
Draft CR 38.101-3 to add DC_1A-7A-28A_n20A |
Vodafone Ireland Plc |
| R4-2220757 |
Draft CR 38.101-3 to add DC_1A-3A-7C-26A_n78(2A) and fall backs |
Ericsson, Telstra |
| 7.6.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218026 |
TR 37.718-11-21 v0.3.0 TR Update: LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-18 |
LG Electronics Deutschland |
| R4-2218027 |
Revised WID on Rel-18 Dual Connectivity (DC) of x bands (x=1,2,3,4) LTE inter-band CA (xDL/1UL) and 2 bands NR inter-band CA (2DL/1UL) |
LG Electronics Deutschland |
| R4-2218028 |
Introduction CR on new NR DC LTE(xDL/1UL)+ NR(2DL/1UL) band combinations in Rel-18 |
LG Electronics Deutschland |
| 7.6.2 |
UE RF requirements without FR2 band |
|
| R4-2218282 |
draftCR to 38.101-3: Addition of DC_40A_n40A |
Nokia, Telefonica |
| R4-2218381 |
Draft CR for 38.101-3 to add DC_3C-20A_n28A-n78A |
Huawei, Hisilicon |
| R4-2218382 |
Draft CR for 38.101-3 to add DC_3A-32A_n1A-n78A and DC_3C-32A_n1A-n78A |
Huawei, Hisilicon |
| R4-2218383 |
Draft CR for 38.101-3 to add DC_7A-32A_n1A-n78A |
Huawei, Hisilicon |
| R4-2218920 |
TP for TR 38.718-11-21 to include DC_3-8-41_n1-n78 |
Ericsson |
| R4-2218921 |
TP for TR 38.718-11-21 to include DC_3-20-41_n1-n78 |
Ericsson |
| R4-2218922 |
TP for TR 38.718-11-21 to include DC_3-41_n1-n78 |
Ericsson |
| R4-2218923 |
TP for TR 38.718-11-21 to include DC_8-41_n1-n78 |
Ericsson |
| R4-2218924 |
TP for TR 38.718-11-21to include DC_20-41_n1-n78 |
Ericsson |
| R4-2218961 |
TP for 37.718-11-21 to include DC_41_n1-n78 |
Ericsson |
| R4-2218965 |
draft CR 38.101-3 to include new EN-DC combinations with band n38 and one more NR band |
Ericsson |
| R4-2219102 |
TP to TR 37.718-11-21 Addition of DC_3_n38-n40 |
Nokia, Telefonica |
| R4-2219103 |
TP to TR 37.718-11-21 Addition of DC_8_n38-n40 |
Nokia, Telefonica |
| R4-2219198 |
draft CR to TS38.101-3 DC_3A-8A_n40A-n79C |
ZTE Corporation |
| R4-2219418 |
TP for TR 37.718-11-21 DC_3A-7A-20A_n1A-n75A and DC_3C-7A-20A_n1A-n75A |
Huawei, HiSilicon |
| R4-2219419 |
TP for TR 37.718-11-21: DC_1A-7A_n75A-n78A |
Huawei, HiSilicon |
| R4-2219420 |
TP for TR 37.718-11-11: DC_3A-7A_n75A-n78A and DC_3C-7A_n75A-n78A |
Huawei, HiSilicon |
| R4-2219421 |
TP for TR 37.718-11-11: DC_1A-3A-7A_n75A-n78A and DC_1A-3C-7A_n75A-n78A |
Huawei, HiSilicon |
| R4-2219422 |
TP for TR 37.718-11-21 DC_1A-3A_n75A-n78A and DC_1C-3A_n75A-n78A |
Huawei, HiSilicon |
| R4-2220603 |
draftCR to 38.101-3: Addition of DC_40A_n40A |
Nokia, Telefonica |
| R4-2220604 |
Draft CR for 38.101-3 to add DC_3C-20A_n28A-n78A |
Huawei, Hisilicon |
| R4-2220605 |
Draft CR for 38.101-3 to add DC_3A-32A_n1A-n78A and DC_3C-32A_n1A-n78A |
Huawei, Hisilicon |
| R4-2220758 |
TP for TR 38.718-11-21 to include DC_3-8-41_n1-n78 |
Ericsson |
| R4-2220759 |
TP for TR 38.718-11-21 to include DC_3-20-41_n1-n78 |
Main Session |
| R4-2220760 |
TP for TR 38.718-11-21 to include DC_3-41_n1-n78 |
Ericsson |
| R4-2220761 |
TP for TR 38.718-11-21 to include DC_8-41_n1-n78 |
Ericsson |
| R4-2220762 |
TP for TR 38.718-11-21to include DC_20-41_n1-n78 |
Ericsson |
| R4-2220764 |
TP for 37.718-11-21 to include DC_41_n1-n78 |
Ericsson |
| R4-2220765 |
draft CR 38.101-3 to include new EN-DC combinations with band n38 and one more NR band |
Ericsson |
| R4-2220768 |
TP to TR 37.718-11-21 Addition of DC_8_n38-n40 |
Nokia, Telefonica |
| R4-2220769 |
TP for TR 37.718-11-21 DC_3A-7A-20A_n1A-n75A and DC_3C-7A-20A_n1A-n75A |
Huawei, HiSilicon |
| R4-2220770 |
TP for TR 37.718-11-11: DC_3A-7A_n75A-n78A and DC_3C-7A_n75A-n78A |
Huawei, HiSilicon |
| R4-2220771 |
TP for TR 37.718-11-11: DC_1A-3A-7A_n75A-n78A and DC_1A-3C-7A_n75A-n78A |
Huawei, HiSilicon |
| R4-2220772 |
TP for TR 37.718-11-21 DC_1A-3A_n75A-n78A and DC_1C-3A_n75A-n78A |
Huawei, HiSilicon |
| 7.6.3 |
UE RF requirements with FR2 band |
|
| R4-2218966 |
draft CR 38.101-3 to include new EN-DC combinations with band n38 and n258 |
Ericsson |
| R4-2219470 |
draft CR for uplink support for DC_3A-3A-7A-7A-8A_n1A-n257M related combinations |
CHTTL |
| R4-2219904 |
Draft CR to TS38.101-3 DC_(n)3AA-n257AJHIJKLM |
Huawei Technologies France |
| R4-2220766 |
draft CR 38.101-3 to include new EN-DC combinations with band n38 and n258 |
Ericsson |
| R4-2220781 |
Draft CR to TS38.101-3 DC_(n)3AA-n257AJHIJKLM |
Huawei Technologies France |
| 7.7.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2219219 |
Revised WID: Rel-18 Dual Connectivity (DC) of x bands (x=1,2,3) LTE inter-band CA (xDL/1UL) and y bands NR inter-band CA (yDL/1UL) |
ZTE Corporation |
| R4-2219220 |
Big CR to reflect the completed DC combinations of x bands (x=1,2,3) LTE inter-band CA (xDL/1UL) and y bands NR inter-band CA (yDL/1UL) |
ZTE Corporation |
| 7.7.2 |
UE RF requirements without FR2 band |
|
| R4-2219199 |
draft CR to TS38.101-3 DC_8A_n39A-n41A-n79A |
ZTE Corporation |
| R4-2219895 |
draft CR to TS38.101-3 DC_(n)3AA-n8A-n77A, DC_(n)3AA-n8A-n77(2A) |
Huawei Technologies France |
| R4-2220777 |
draft CR to TS38.101-3 DC_(n)3AA-n8A-n77A, DC_(n)3AA-n8A-n77(2A) |
Huawei Technologies France |
| 7.7.3 |
UE RF requirements with FR2 band |
|
| R4-2219897 |
draft CR to TS38.101-3 DC_(n)3AA-n8A-n77A-n257AGHIJKLM, DC_(n)3AA-n8A-n77(2A)-n257AGHIJKLM |
Huawei Technologies France |
| R4-2219898 |
Draft CR to TS38.101-3 DC_(n)3AA-n8A-n257AGHIJKLM |
Huawei Technologies France |
| R4-2219903 |
Draft CR to TS38.101-3 DC_(n)3AA-n77A-n257AJHIJKLM, DC_(n)3AA-n77(2A)-n257A |
Huawei Technologies France |
| R4-2220778 |
draft CR to TS38.101-3 DC_(n)3AA-n8A-n77A-n257AGHIJKLM, DC_(n)3AA-n8A-n77(2A)-n257AGHIJKLM |
Huawei Technologies France |
| R4-2220779 |
Draft CR to TS38.101-3 DC_(n)3AA-n8A-n257AGHIJKLM |
Huawei Technologies France |
| R4-2220780 |
Draft CR to TS38.101-3 DC_(n)3AA-n77A-n257AJHIJKLM, DC_(n)3AA-n77(2A)-n257A |
Huawei Technologies France |
| 7.8.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218764 |
Revised Rel-18 WID on DC of x LTE bands and y NR bands with z bands DL and 3 bands UL |
Samsung |
| R4-2218765 |
Big CR on introduction of completed DC of x LTE bands and y NR bands with z bands DL and 3 bands UL |
Samsung |
| 7.9.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218944 |
Revised WID NR Intra-band Rel-18 |
Ericsson |
| R4-2218945 |
big CR 38.101-1 new combinations Rel-18 NR Intra-band |
Ericsson |
| R4-2218946 |
big CR 38.101-2 new combinations Rel-18 NR Intra-band |
Ericsson |
| R4-2218947 |
TR 38.718-01-01 v0.1.0 Rel-18 NR Intra-band |
Ericsson |
| R4-2218951 |
draft CR rewriting of FR2 Intra-band table to include more CC's |
Ericsson |
| 7.9.2 |
UE RF requirements for FR1 |
|
| R4-2218520 |
TP for TR 38.718-01-01: CA_n78(A-C) |
SK Telecom |
| R4-2219109 |
draftCR_additions_to_CA_n41C in UL |
Nokia, T-Mobile |
| R4-2220783 |
draftCR_additions_to_CA_n41C in UL |
Nokia, T-Mobile |
| 7.9.3 |
UE RF requirements for FR2 |
|
| R4-2218952 |
draft CR 38.101-2 to add new Intra-band CA n260 configurations |
Ericsson, Verizon |
| R4-2220782 |
draft CR 38.101-2 to add new Intra-band CA n260 configurations |
Ericsson, Verizon |
| 7.10.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2219214 |
Revised WID:Rel-18 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
| R4-2219215 |
TR38.718-02-01 skeleton v0.3.0: Rel-18 NR Inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
| R4-2219216 |
Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-1 |
ZTE Corporation |
| R4-2219217 |
Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-2 |
ZTE Corporation |
| R4-2219218 |
Big CR to reflect the completed NR inter band CA DC combinations for 2 bands DL with up to 2 bands UL into TS 38.101-3 |
ZTE Corporation |
| 7.10.2 |
UE RF requirements without FR2 band |
|
| R4-2218646 |
TP for 38.718-02-01 CA_n3A-n41C with UL_n41C |
CMCC |
| R4-2218673 |
DraftCR for 38.101-1: Add band n48 uplink configurations |
Verizon, Samsung, Ericsson |
| R4-2218954 |
Rel-18 draft CR 38.101-1 for two band CA corrections |
Ericsson |
| R4-2219105 |
draftCR_additions_to_CA_n41_n66 |
Nokia, T-Mobile |
| R4-2219106 |
draftCR_additions_to_CA_n41_n71 |
Nokia, T-Mobile |
| R4-2219108 |
draftCR_additions_to_CA_n41_n77 |
Nokia, T-Mobile |
| R4-2219110 |
TP to TR 38.718-02-01 Addition of CA_n25-n85 |
Nokia, T-Mobile |
| R4-2219111 |
TP to TR 38.718-02-01 Addition of CA_n41-n85 |
Nokia, T-Mobile |
| R4-2219112 |
TP to TR 38.718-02-01 Addition of CA_n66-n85 |
Nokia, T-Mobile |
| R4-2219113 |
TP to TR 38.718-02-01 Addition of CA_n71-n85 |
Nokia, T-Mobile |
| R4-2219114 |
TP to TR 38.718-02-01 Addition of CA_n77-n85 |
Nokia, T-Mobile |
| R4-2219200 |
draft CRto TS 38.101-1_include n34A-n41C |
ZTE Corporation |
| R4-2219201 |
draft CRto TS 38.101-1_include n39A-n79C |
ZTE Corporation |
| R4-2219572 |
Draft CR for 38.101-3 to add configuration CA_n1A-n257(2A)(2G)(A-G) |
Huawei, HiSilicon |
| R4-2219573 |
Draft CR for 38.101-3 to add configuration CA_n1A-n258(2A)(2G)(A-G) |
Huawei, HiSilicon |
| R4-2219574 |
Draft CR for 38.101-3 to add configuration CA_n3A-n257(2G)(A-G) |
Huawei, HiSilicon |
| R4-2219575 |
Draft CR for 38.101-3 to add configuration CA_n3A-n258(2G)(A-G) |
Huawei, HiSilicon |
| R4-2219576 |
Draft CR for 38.101-3 to add configuration CA_n77A-n257(2A)(2G)(A-G) |
Huawei, HiSilicon |
| R4-2219577 |
Draft CR for 38.101-3 to add configuration CA_n77A-n258(2G)(A-G) |
Huawei, HiSilicon |
| R4-2219578 |
Draft CR for 38.101-3 to add configuration CA_n78A-n257(2A)(2G)(A-G) |
Huawei, HiSilicon |
| R4-2219579 |
Draft CR for 38.101-3 to add configuration CA_n78A-n258(2G)(A-G) |
Huawei, HiSilicon |
| R4-2220564 |
DraftCR for 38.101-1: Add band n48 uplink configurations |
Verizon, Samsung, Ericsson |
| R4-2220784 |
TP to TR 38.718-02-01 Addition of CA_n25-n85 |
Nokia, T-Mobile |
| R4-2220785 |
TP to TR 38.718-02-01 Addition of CA_n41-n85 |
Nokia, T-Mobile |
| R4-2220786 |
TP to TR 38.718-02-01 Addition of CA_n66-n85 |
Nokia, T-Mobile |
| R4-2220787 |
TP to TR 38.718-02-01 Addition of CA_n77-n85 |
Nokia, T-Mobile |
| R4-2220788 |
draft CRto TS 38.101-1_include n34A-n41C |
ZTE Corporation |
| R4-2220789 |
Draft CR for 38.101-3 to add configuration CA_n3A-n257(2G)(A-G) |
Huawei, HiSilicon |
| 7.10.3 |
UE RF requirements with FR2 band |
|
| R4-2218955 |
Rel-18 draft CR 38.101-3 for two band CA corrections |
Ericsson |
| R4-2219202 |
draft CRto TS 38.101-3_include n34A-n258B/C/D/E/F/G/H/I/J/K/L/M |
ZTE Corporation |
| R4-2219203 |
draft CRto TS 38.101-3_include n41A-n258B/C/D/E/F/G/H/I/J/K/L/M |
ZTE Corporation |
| R4-2219297 |
draft CR 38.101-2 to add CA_n258-n260 configurations |
Ericsson, TMUS |
| R4-2219298 |
draft CR 38.101-2 to add CA_n41-n258 configurations |
Ericsson, TMUS |
| R4-2219299 |
draft CR 38.101-2 to add CA_n41-n260 configurations |
Ericsson, TMUS |
| R4-2220790 |
draft CR 38.101-2 to add CA_n258-n260 configurations |
Ericsson, TMUS |
| R4-2220791 |
draft CR 38.101-2 to add CA_n41-n258 configurations |
Ericsson, TMUS |
| R4-2220792 |
draft CR 38.101-2 to add CA_n41-n260 configurations |
Ericsson, TMUS |
| 7.11.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2219763 |
TR38.718-03-01 v0.3.0 on Rel-18 NR Inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
| R4-2219764 |
Big CR to reflect the completed NR inter-band CA DC combinations for 3 bands DL with x bands UL (x=1,2) into TS 38.101-1 |
ZTE Corporation |
| R4-2219765 |
Big CR to reflect the completed NR inter-band CA DC combinations for 3 bands DL with x bands UL (x=1,2) into TS 38.101-3 |
ZTE Corporation |
| R4-2219766 |
Revised WID:Rel-18 NR Inter-band Carrier Aggregation/Dual Connectivity for 3 bands DL with x bands UL (x=1,2) |
ZTE Corporation |
| 7.11.2 |
UE RF requirements without FR2 band |
|
| R4-2218077 |
TP for TR 38.718-03-01: CA_n48-n70-n77 |
Dish Network, Samsung |
| R4-2218078 |
TP for TR 38.718-03-01: CA_n66-n70-n77 |
Dish Network, Samsung |
| R4-2218079 |
TP for TR 38.718-03-01: CA_n70-n71-n77 |
Dish Network, Samsung |
| R4-2218080 |
Draft CR for TS 38.101-1 to add CA_n48(2A)-n70A-n77A, CA_n48(2A)-n71A-n77A, CA_n66(2A)-n70A-n77A |
Dish Network, Samsung |
| R4-2218249 |
Draft CR for TS 38.101-1: Support of n77(3A) in CA_n1-n3-n77, n1-n28-n77 and n1-n41-n77 |
SoftBank Corp. |
| R4-2218250 |
Draft CR for TS 38.101-1: Support of DC_n3-n41-n79 |
SoftBank Corp. |
| R4-2218672 |
DraftCR for 38.101-1: Add additional downlink and uplink configurations |
Verizon, Samsung, Ericsson |
| R4-2218968 |
TP for 38.718-03-01 to include CA_n1-n3-n38 |
Ericsson |
| R4-2218969 |
TP for 38.718-03-01 to include CA_n1-n7-n38 |
Ericsson |
| R4-2218970 |
TP for 38.718-03-01 to include CA_n3-n7-n38 |
Ericsson |
| R4-2218971 |
TP for 38.718-03-01 to include CA_n3-n28-n38 |
Ericsson |
| R4-2218972 |
TP for 38.718-03-01 to include CA_n7-n28-n38 |
Ericsson |
| R4-2219104 |
draftCR_additions_to_CA_n25_n41_n66 |
Nokia, T-Mobile |
| R4-2219107 |
draftCR_additions_to_CA_n41_n71_n77 |
Nokia, T-Mobile |
| R4-2219204 |
TP for TR 38.718-03-01_3DL_2UL CA_n39A-n41A-n79 |
ZTE Corporation |
| R4-2219274 |
DraftCR add uplink CA_n78(2A) to the existing 3 bands DL CA combinations |
Huawei, HiSilicon, BT |
| R4-2220565 |
DraftCR for 38.101-1: Add additional downlink and uplink configurations |
Verizon, Samsung, Ericsson |
| R4-2220793 |
TP for TR 38.718-03-01: CA_n48-n70-n77 |
Dish Network, Samsung |
| R4-2220794 |
TP for TR 38.718-03-01: CA_n66-n70-n77 |
Dish Network, Samsung |
| R4-2220795 |
TP for TR 38.718-03-01: CA_n70-n71-n77 |
Dish Network, Samsung |
| R4-2220796 |
TP for 38.718-03-01 to include CA_n1-n3-n38 |
Ericsson |
| R4-2220797 |
TP for 38.718-03-01 to include CA_n1-n7-n38 |
Ericsson |
| R4-2220798 |
TP for 38.718-03-01 to include CA_n3-n7-n38 |
Ericsson |
| R4-2220799 |
TP for 38.718-03-01 to include CA_n3-n28-n38 |
Ericsson |
| R4-2220800 |
TP for 38.718-03-01 to include CA_n7-n28-n38 |
Ericsson |
| R4-2220801 |
TP for TR 38.718-03-01_3DL_2UL CA_n39A-n41A-n79 |
ZTE Corporation |
| 7.11.3 |
UE RF requirements with FR2 band |
|
| R4-2218261 |
Draft CR for TS 38.101-3: Support of UL configurations in CA_n1-n77-n257 and n41-n77-n257 |
SoftBank Corp. |
| R4-2218623 |
DraftCR for 38.101-3: NR FR1 and FR2 inter-band CA DC combinations for 3 bands DL with single and 2 bands UL |
Verizon, Samsung, Ericsson |
| R4-2218956 |
Rel-18 draft CR 38.101-3 for three band CA corrections |
Ericsson |
| 7.12.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2219300 |
Revised WID Rel-18 NR Inter-band CA/DC for y bands DL with x bands UL (y=4,5,6, x=1,2) |
Ericsson |
| R4-2219301 |
big CR 38.101-1 new combinations Rel-18 NR Inter-band CA/DC for y bands DL with x bands UL (y=4,5,6, x=1,2) |
Ericsson |
| R4-2219302 |
big CR 38.101-3 new combinations Rel-18 NR Inter-band CA/DC for y bands DL with x bands UL (y=4,5,6, x=1,2) |
Ericsson |
| 7.12.2 |
UE RF requirements without FR2 band |
|
| R4-2218086 |
Draft CR for TS 38.101-1 to add 4 Band CA combinations |
Dish Network, Samsung |
| R4-2218251 |
Draft CR for TS 38.101-1: Support of n77(2A) in CA_n1-n3-n77-n79 and n1-n28-n77-n79 |
SoftBank Corp. |
| R4-2218252 |
Draft CR for TS 38.101-1: Support of CA_n1-n3-n41-n79, n3-n28-n41-n79 and n3-n41-n77-n79 |
SoftBank Corp. |
| R4-2218254 |
Draft CR for TS 38.101-1: Support of DC_n1-n28-n41-n79, n1-n41-n77-n79 and n28-n41-n77-n79 |
SoftBank Corp. |
| R4-2218256 |
Draft CR for TS 38.101-1: Support of CA_n1-n3-n28-n41-n79, n1-n3-n28-n77-n79, n1-n3-n41-n77-n79 and n1-n28-n41-n77-n79 |
SoftBank Corp. |
| R4-2218259 |
Draft CR for TS 38.101-1: Addition of missing information for 4 and 5 bands CA combinations |
SoftBank Corp. |
| R4-2218617 |
draft CR for introducing CA_n1-n3-n7-n8-n78 |
CHTTL |
| R4-2218915 |
Draft CR to add CA_n1A-n3A-n7A-n26A-n78(2A), CA_n1A-n3A-n7B-n26A-n78(2A) and fallbacks |
Ericsson, Telstra |
| R4-2218973 |
draft CR 38.101-1 to include NR CA combinations with band n38 |
Ericsson |
| R4-2219275 |
DraftCR add uplink CA_n78(2A) to the existing 4 and 5 bands DL CA combinations |
Huawei, HiSilicon, BT |
| R4-2219293 |
draft CR 38101-1 to add CA_n2-n5-n30-n66-n77 |
Ericsson, AT&T |
| R4-2219294 |
draft CR 38101-1 to add CA_n2-n12-n30-n66-n77 |
Ericsson, AT&T |
| R4-2219295 |
draft CR 38101-1 to add CA_n2-n14-n30-n66-n77 |
Ericsson, AT&T |
| R4-2219296 |
draft CR 38101-1 to add CA_n2-n30-n66-n77 |
Ericsson, AT&T |
| 7.12.3 |
UE RF requirements with FR2 band |
|
| R4-2218253 |
Draft CR for TS 38.101-3: Support of CA_n3-n41-n79-n257 |
SoftBank Corp. |
| R4-2218255 |
Draft CR for TS 38.101-3: Support of CA_n1-n3-n28-n41-n257, n1-n3-n28-n77-n257 and n1-n3-n77-n79-n257 |
SoftBank Corp. |
| R4-2218257 |
Draft CR for TS 38.101-3: Support of CA_n1-n3-n41-n77-n257, n1-n28-n41-n77-n257 and n1-n28-n41-n79-n257 |
SoftBank Corp. |
| R4-2218258 |
Draft CR for TS 38.101-3: Support of CA_n1-n28-n77-n79-n257, n1-n41-n77-n79-n257 and n3-n28-n41-n77-n257 |
SoftBank Corp. |
| R4-2218260 |
Draft CR for TS 38.101-3: Addition of missing information for 4 and 5 bands CA combinations |
SoftBank Corp. |
| R4-2218262 |
Draft CR for TS 38.101-3: Support of n77(2A) in CA_n1-n28-n77-n257, n1-n41-n77-n257 and n1-n77-n79-n257 |
SoftBank Corp. |
| 7.13.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2219564 |
Revised WID on Band combinations for SA NR Supplementary uplink (SUL), NSA NR SUL, NSA NR SUL with UL sharing from the UE perspective (ULSUP) |
Huawei, HiSilicon |
| R4-2219565 |
Draft TR 37.718-00-00 v0.2.0 |
Huawei, HiSilicon |
| R4-2219566 |
Big CR on Introduction of completed SUL band combinations into TS 38.101-1 |
Huawei, HiSilicon |
| 7.13.2 |
UE RF requirements |
|
| R4-2219755 |
Draft CR for TS 38.101-1 to update delta TIB and RIB template for SUL combinations |
ZTE Corporation |
| R4-2219757 |
TP for TR 37.718-00-00 on delta TIB and RIB template for SUL combinations |
ZTE Corporation |
| 7.14.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218442 |
TR 37.878 v0.2.0 TR for R18 Uu+V2X band combinations |
CATT |
| R4-2218443 |
Big CR for TS 38.101-1, Introduction of new R18 Uu+V2X band combinations |
CATT |
| R4-2218444 |
Big CR for TS 38.101-3, Introduction of new R18 Uu+V2X band combinations |
CATT |
| 7.14.2 |
UE RF requirements |
|
| R4-2218196 |
Draft CR for TS 38.101-3, Introduce new band combination of V2X_n34A_47A and 34A_n47A |
Qualcomm Technologies Int |
| R4-2218197 |
Draft CR for TS 38.101-1, Introduce new band combination V2X_n34A-n47A |
Qualcomm Technologies Int |
| R4-2218198 |
TP updates for TR37.878 |
Qualcomm Technologies Int |
| R4-2218445 |
Draft CR for TS 38.101-1, Introduce new band combination of V2X_n3A-n47A |
CATT |
| R4-2218446 |
Draft CR for TS 38.101-3, Introduce new band combinations of V2X_n3A_47A |
CATT |
| R4-2218447 |
Draft CR for TS 38.101-1, Introduce new band combination of V2X_n34A-n47A |
CATT |
| R4-2218448 |
Draft CR for TS 38.101-3, Introduce new band combinations of V2X_n34A_47A and V2X_34A_n47A |
CATT |
| R4-2220459 |
Draft CR for TS 38.101-1, Introduce new band combination of V2X_n3A-n47A |
CATT |
| R4-2220460 |
Draft CR for TS 38.101-3, Introduce new band combinations of V2X_n3A_47A |
CATT |
| R4-2220461 |
Draft CR for TS 38.101-3, Introduce new band combination of V2X_n34A_47A and 34A_n47A |
Qualcomm Technologies Int |
| R4-2220462 |
Draft CR for TS 38.101-1, Introduce new band combination of V2X_n34A-n47A |
CATT |
| 7.15.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218268 |
Revised WID: High-power UE operation for fixed-wireless/vehicle-mounted use cases in LTE bands and NR bands |
Nokia |
| R4-2218269 |
TR 37.829 v0.2.0 |
Nokia |
| R4-2218270 |
TR 37.829 v0.3.0 |
Nokia |
| R4-2218271 |
draft CR for FWA MPR and A-MPR for n71 and n85 |
Nokia |
| R4-2218272 |
Big CR for FWA MPR and A-MPR for n71 and n85 |
Nokia |
| R4-2220463 |
draft CR for FWA MPR and A-MPR for n71 and n85 |
Nokia |
| 7.15.2 |
UE RF requirements |
|
| R4-2218283 |
PC1 MPR with edge region |
Nokia, Nokia Shanghai Bell |
| R4-2218323 |
TP to TR 37.829: PC1 A-MPR and MPR for bands n71 and n85 |
Nokia, Nokia Shanghai Bell |
| R4-2220024 |
Additional Power Class Configurations for FWA |
T-Mobile USA Inc. |
| 7.16.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218068 |
Workplan for High Power UE support for NR bands n100 and n101 for Rail Mobile Radio (RMR) in Europe |
Union Inter. Chemins de Fer |
| 7.17.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218948 |
Revised WID on PC1.5 and PC2 EN-DC combinations with xLTE bands + yNR bands |
Ericsson |
| R4-2218949 |
big CR 38.101-3 new combinations Rel-18 EN-DC HPUE |
Ericsson |
| R4-2218950 |
TR 38.898 v0.1.0 Rel-18 High power UE for FR1 for DC_R18_xBLTE_yBNR_zDLnUL |
Ericsson |
| 7.17.2 |
UE RF requirements |
|
| R4-2218221 |
TP for PC2 DC_1_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2218222 |
TP for PC2 DC_3_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2218223 |
TP for PC2 DC_19_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2218224 |
TP for PC2 DC_21_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2220466 |
TP for PC2 DC_1_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2220467 |
TP for PC2 DC_3_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2220468 |
TP for PC2 DC_19_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| R4-2220469 |
TP for PC2 DC_21_n79 for TR 38.898 |
NTT DOCOMO, INC. |
| 7.18.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2219389 |
WID on HPUE_NR_FR1_TDD_intra_CA_R18 |
Huawei,HiSilicon |
| R4-2219390 |
Big CR on TS38.101-1 Addition of intra-band CA Combinations with PC2 and PC1.5 |
Huawei,HiSilicon |
| R4-2219391 |
TR 38.897 skeleton |
Huawei,HiSilicon |
| R4-2220577 |
TR 38.897 skeleton |
Huawei,HiSilicon |
| 7.18.2 |
UE RF requirements with PC2 and PC1.5 |
|
| R4-2218208 |
Discussion on PC1.5 power class fallback logic relevant to SAR issue |
Mediatek India Technology Pvt. |
| R4-2219388 |
Draft CR on TS38.101-1 Addition of intra-band CA Combinations with PC1.5 |
Huawei,HiSilicon |
| 7.19.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218378 |
Revised WID: Rel-18 High power UE (power class 1,5 and 2) for a single FR1 NR TDD band in UL of NR inter-band CA/DC combinations with/without NR SUL (supplementary uplink) with y bands downlink (y=2,3,4,5,6) and x bands uplink (x=1,2) |
China Telecom |
| R4-2218379 |
Big CR to 38.101-1 Introduce RF requirements for HPUE inter- band CA with y(y=2,3,4) bands downlink and x bands uplink (x =1,2) |
China Telecom |
| R4-2219272 |
TR for High power UE for FR1 NR inter-band CA/DC or NR SUL band combination with y (1
| Huawei, HiSilicon, China Telecom |
|
| R4-2220844 |
TR for High power UE for FR1 NR inter-band CA/DC or NR SUL band combination with y (1
| Huawei, HiSilicon, China Telecom |
|
| 7.19.2 |
UE RF requirements with PC2 and PC1.5 |
|
| R4-2218037 |
DraftCR 38.101-1 Addition of PC2 CA Combinations |
AT&T |
| R4-2218219 |
TP for HPUE CA_n77-n79 with 1UL for TR 38.899 |
NTT DOCOMO, INC. |
| R4-2218220 |
TP for HPUE CA_n78-n79 with 1UL for TR 38.899 |
NTT DOCOMO, INC. |
| R4-2219996 |
Draft CR for 38.101-1: T-Mobile 4 Band DL HPUE combinations |
T-Mobile USA |
| R4-2219997 |
Draft CR for 38.101-1: CA_n25(2A)-n77(2A) with PC2 UL CA_n25A-n77A |
T-Mobile USA |
| R4-2219998 |
Draft CR for 38.101-1: PC2 2B UL CA for combinations with DL CA_n41-n66-n71 |
T-Mobile USA |
| R4-2219999 |
Draft CR for 38.101-1: CA_n71-n77 with PC2 2 band UL CA |
T-Mobile USA |
| R4-2220000 |
Draft CR for 38.101-1: HPUE Big CR for T-Mobile USA combinations |
T-Mobile USA |
| R4-2220003 |
TP for TR38.899 for DL CA_n25-n41-n66 with PC2 2BUL |
T-Mobile USA |
| R4-2220004 |
TP for TR38.899 for DL CA_n25-n41-n71 with PC2 2BUL |
T-Mobile USA |
| R4-2220005 |
TP for TR38.899 for DL CA_n25-n41-n77 with PC2 2BUL |
T-Mobile USA |
| R4-2220006 |
TP for TR38.899 for DL CA_n25-n66-n77 with PC2 2BUL |
T-Mobile USA |
| R4-2220007 |
TP for TR38.899 for DL CA_n25-n71-n77 with PC2 2BUL |
T-Mobile USA |
| R4-2220008 |
TP for TR38.899 for DL CA_n41-n66-n71 with PC2 2BUL |
T-Mobile USA |
| R4-2220009 |
TP for TR38.899 for DL CA_n41-n66-n77 with PC2 2BUL |
T-Mobile USA |
| R4-2220010 |
TP for TR38.899 for DL CA_n41-n71-n77 with PC2 2BUL |
T-Mobile USA |
| R4-2220011 |
TP for TR38.899 for DL CA_n66-n71-n77 with PC2 2BUL |
T-Mobile USA |
| R4-2220012 |
TP for TR38.899 for DL CA_n25-n41C with PC2 UL CA_n41C |
T-Mobile USA |
| R4-2220013 |
TP for TR38.899 for DL CA_n41C-n66 with PC2 UL CA_n41C |
T-Mobile USA |
| R4-2220014 |
TP for TR38.899 for DL CA_n41C-n71 with PC2 UL CA_n41C |
T-Mobile USA |
| R4-2220015 |
TP for TR38.899 for DL CA_n41C-n77 with PC2 UL CA_n41C |
T-Mobile USA |
| R4-2220470 |
TP for HPUE CA_n77-n79 with 1UL for TR 38.899 |
NTT DOCOMO, INC. |
| R4-2220471 |
TP for HPUE CA_n78-n79 with 1UL for TR 38.899 |
NTT DOCOMO, INC. |
| R4-2220472 |
TP for TR38.899 for DL CA_n25-n41-n66 with PC2 2BUL |
T-Mobile USA |
| R4-2220473 |
Draft CR for 38.101-1: PC2 2B UL CA for combinations with DL CA_n41-n66-n71 |
T-Mobile USA |
| R4-2220474 |
Draft CR for 38.101-1: HPUE Big CR for T-Mobile USA combinations |
T-Mobile USA |
| R4-2220475 |
TP for TR38.899 for DL CA_n25-n41-n77 with PC2 2BUL |
T-Mobile USA |
| R4-2220476 |
TP for TR38.899 for DL CA_n25-n66-n77 with PC2 2BUL |
T-Mobile USA |
| R4-2220477 |
TP for TR38.899 for DL CA_n25-n71-n77 with PC2 2BUL |
T-Mobile USA |
| R4-2220478 |
TP for TR38.899 for DL CA_n41-n66-n77 with PC2 2BUL |
T-Mobile USA |
| R4-2220479 |
TP for TR38.899 for DL CA_n41-n71-n77 with PC2 2BUL |
T-Mobile USA |
| R4-2220480 |
TP for TR38.899 for DL CA_n66-n71-n77 with PC2 2BUL |
T-Mobile USA |
| 7.20.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218610 |
Revised WID on High power UE for FR1 for inter-band NR_CADC_R18_yBDL_xBUL with power class 2 on single carrier uplink on FDD band |
China Unicom |
| R4-2218620 |
BigCR for High power UE for inter-band CA with power class 2 on single carrier uplink on FDD band |
China Unicom |
| 7.20.2 |
UE RF requirements |
|
| R4-2218621 |
Draft CR for HPUE for CA with PC2 on FDD carrier CA_n1A-n78A and CA_n3A-n78A |
China Unicom |
| R4-2220481 |
Draft CR for HPUE for CA with PC2 on FDD carrier CA_n1A-n78A and CA_n3A-n78A |
China Unicom |
| 7.21.2 |
UE RF requirements |
|
| R4-2218640 |
Discussion on PC1.5 SAR issue |
CMCC |
| R4-2218880 |
Further discussion on the dutycycle of High power UE |
vivo |
| R4-2219268 |
Discussion on the duty cycle scheme |
Huawei, HiSilicon |
| R4-2219981 |
Preliminary measured back-off results for NS_50 PC1.5 A-MPR for n39 |
Skyworks Solutions Inc. |
| R4-2220001 |
[Draft] LS on Duty Cycle capability for PC1.5 |
T-Mobile USA |
| R4-2220002 |
Proposal to clarify Power Class control logic |
T-Mobile USA, Apple, Verizon, Skyworks Solutions, Inc. |
| R4-2220465 |
[Draft] LS on Duty Cycle capability for PC1.5 |
T-Mobile USA |
| R4-2220488 |
Way forward on remaining UE requirements for n105 |
Ercicsson |
| R4-2220602 |
Proposal to clarify Power Class control logic |
T-Mobile USA, Apple, Verizon, Skyworks Solutions, Inc. |
| R4-2220807 |
LS on Duty Cycle capability for PC1.5 |
T-Mobile USA |
| 7.22.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218609 |
Revised WID on High power UE for FR1 for FDD single band(s) with PC2 |
China Unicom |
| R4-2218614 |
BigCR for High power UE for FDD single band PC2 |
China Unicom |
| R4-2218618 |
TR 38.896 v0.1.0 HPUE_NR_FR1_FDD_R18 |
China Unicom |
| 7.22.2 |
UE RF requirements |
|
| R4-2218113 |
PC2 FDD bands MSD with 1Tx |
Apple |
| R4-2219213 |
TP for TR 38.896 to include HPUE single band n8 |
ZTE Corporation, China Unicom |
| R4-2219723 |
Preliminary REFSENS results for 1Tx and 2Tx PC2 FDD bands |
Skyworks Solutions Inc. |
| R4-2219869 |
Discussion on PC2 bands n8 and n28 reference sensitivity degradation |
Mediatek India Technology Pvt. |
| R4-2220482 |
TP for TR 38.896 to include HPUE single band n8 |
ZTE Corporation, China Unicom |
| 7.23.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218608 |
TR 37.877 0.2.0 draft TR for Rel-18 downlink interruption for NR and EN-DC band combinations at dynamic Tx switching |
China Telecom |
| 7.23.2 |
UE RF requirements |
|
| R4-2218607 |
TP to 37.877 DL interruption clarification for CA_n3-n5-n78 at dynamic Tx switching |
China Telecom |
| 7.24.1 |
Rapporteur Input (WID/TR/CR) |
|
| R4-2219491 |
CR for 38.101-1: introduce UL MIMO configurations for band n40 |
Huawei, HiSilicon |
| R4-2219492 |
WID revision: Additional NR bands for UL-MIMO in Rel-18 |
Huawei, HiSilicon |
| R4-2219493 |
Big CR for 38.101-1 introduce UL MIMO configurations for Rel-18 |
Huawei, HiSilicon |
| 7.24.2 |
UE RF requirements |
|
| R4-2218736 |
Draft CR for n8 PC3 UL MIMO |
China Unicom, CHTTL |
| R4-2220483 |
Draft CR for n8 PC3 UL MIMO |
China Unicom, CHTTL |
| 7.25.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2218503 |
Revised Basket WID on adding channel bandwidth support to existing NR bands |
Ericsson |
| 7.25.2 |
UE RF requirements |
|
| R4-2218505 |
Big CR to TS 38.101-1: Adding channel BW support in existing NR bands |
Ericsson |
| R4-2218635 |
Draft CR for 38.101-1: Adding 35 MHz for n39 and n98 |
CMCC |
| 7.25.3 |
BS RF requirements |
|
| R4-2218504 |
Big CR to TS 38.104: Adding channel BW support in existing NR bands |
Ericsson |
| R4-2218636 |
Draft CR for 38.104: Adding 35 MHz for n39 and n98 |
CMCC |
| 7.26.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2219414 |
Revised WID for Rel-18 Basket Simultaneous Rx/Tx |
Huawei, HiSilicon |
| R4-2219415 |
TR 38.xxx v0.1.0 Rel-18 Requirements for simultaneous Rx/Tx band combinations for NR CA/DC, NR SUL and LTE/NR DC |
Huawei, HiSilicon |
| 7.26.2 |
Identification of simultaneous Rx/Tx capability for band combinations and UE RF requirements |
|
| R4-2218106 |
On simultaneous Rx/Tx for NR inter-band combinations |
Apple |
| R4-2218925 |
Discussion simultaneous Rx/Tx inter-band combinations for CA_n40-n41 |
MediaTek Inc. |
| R4-2219212 |
TP for TR 38.894 to include simultaneous Rx/Tx CA_n39-n41 |
ZTE Corporation |
| R4-2219416 |
TP for TR38.894: CA_n39A-n41A ,CA_n34A-n41A, CA_n40A-n41A, CA_n7A-n40A |
Huawei, HiSilicon |
| R4-2219417 |
Discussion on UE supporting CA_n39A-n41Awith simultaneous Rx/Tx |
Huawei, HiSilicon |
| R4-2220484 |
TP for TR 38.894 to include simultaneous Rx/Tx CA_n39-n41 |
ZTE Corporation |
| R4-2220485 |
TP for TR38.894: CA_n39A-n41A ,CA_n34A-n41A, CA_n40A-n41A, CA_n7A-n40A |
Huawei, HiSilicon |
| 7.27.1 |
General and work plan |
|
| R4-2218046 |
TR 38.892 |
Spark NZ Ltd |
| R4-2218768 |
Text Proposals for TR 38 892 |
Spark NZ Ltd |
| 7.27.2 |
Band parameters and UE RF requirements |
|
| R4-2218047 |
UE RF parameters for n 105 |
Spark NZ Ltd |
| R4-2218049 |
UE RF parameters for n 105 |
Spark NZ Ltd |
| R4-2218050 |
Text proposals for TR 38 892 |
Spark NZ Ltd |
| R4-2218127 |
600M_APT_REFSENS_IBB |
Murata Manufacturing Co Ltd. |
| R4-2218386 |
REFSENS and other UE requirements for n105 |
Skyworks Solutions Inc. |
| R4-2218810 |
REFSENS for APT-600 |
MediaTek Inc. |
| R4-2218824 |
Asymmetric bandwidths for APT 600 MHz and the REFSENS requirement |
Ericsson |
| R4-2219603 |
Discussion on the concept of variable duplex |
OPPO |
| R4-2219707 |
UE REFSENS and asymmetric channel bandwidth |
Nokia, Nokia Shanghai Bell |
| R4-2219984 |
In band blocking for APT 600 |
Qualcomm Incorporated, Skyworks Solutions, Inc. |
| R4-2219985 |
Variable duplex for the APT 600 MHz band |
Qualcomm Incorporated |
| R4-2219986 |
Introduction of APT 600 MHz band |
Qualcomm Incorporated |
| R4-2220016 |
TP for TR 38.892: n105 compatibility with legacy n71 UEs |
T-Mobile USA |
| R4-2220486 |
Text proposals for TR 38 892 |
Spark NZ Ltd, Nokia |
| R4-2220487 |
Introduction of APT 600 MHz band |
Qualcomm Incorporated |
| R4-2220843 |
Introduction of APT 600 MHz band |
Qualcomm Incorporated |
| 7.27.3 |
BS RF requirements and conformance testing |
|
| R4-2218498 |
CR to TS 38.141-1: Introduction of NR band n105 |
Ericsson |
| R4-2218499 |
CR to TS 37.105: Introduction of NR band n105 |
Ericsson |
| R4-2219349 |
CR to TS38.104 the introduction of APT600MHz |
ZTE Corporation |
| R4-2219350 |
CR to TS37.145-1 the introduction of APT600MHz |
ZTE Corporation |
| R4-2219351 |
CR to TS37.145-2 the introduction of APT600MHz |
ZTE Corporation |
| R4-2219352 |
draft CR to TS38.106 the introduction of APT600MHz |
ZTE Corporation |
| R4-2219860 |
TP to TR 38.892: BS requirements for APT 600 MHz NR band |
Nokia, Nokia Shanghai Bell |
| R4-2219861 |
CR to 37.104 on introduction of Band n105 |
Nokia, Nokia Shanghai Bell |
| R4-2219862 |
CR to 37.141 on introduction of Band n105 |
Nokia, Nokia Shanghai Bell |
| R4-2219863 |
CR to 38.141-2 on introduction of Band n105 |
Nokia, Nokia Shanghai Bell |
| R4-2220489 |
CR to TS 38.141-1: Introduction of NR band n105 |
Ericsson |
| R4-2220490 |
CR to 37.104 on introduction of Band n105 |
Nokia, Nokia Shanghai Bell |
| R4-2220491 |
CR to 37.141 on introduction of Band n105 |
Nokia, Nokia Shanghai Bell |
| R4-2220860 |
CR to 37.141 on introduction of Band n105 |
Nokia, Nokia Shanghai Bell |
| R4-2220861 |
CR to TS38.104 the introduction of APT600MHz |
ZTE Corporation |
| R4-2220862 |
CR to TS37.145-1 the introduction of APT600MHz |
ZTE Corporation |
| R4-2220863 |
CR to TS37.145-2 the introduction of APT600MHz |
ZTE Corporation |
| 7.27.4 |
RRM requirements |
|
| R4-2218500 |
CR to TS 38.133: Introduction of NR band n105 |
Ericsson |
| R4-2220492 |
CR to TS 38.133: Introduction of NR band n105 |
Ericsson |
| 7.27.5 |
Moderator summary and conclusions |
|
| R4-2220098 |
Topic summary for [105][118] NR_600MHz_APT_part1 |
Moderator (Ericsson) |
| R4-2220099 |
Topic summary for [105][119] NR_600MHz_APT_part2 |
Moderator (Ericsson) |
| 7.28 |
Introduction of evolved shared spectrum bands |
|
| R4-2219081 |
Discussion on NS extension for NR-U |
Nokia, Nokia Shanghai Bell |
| R4-2219164 |
Discussion on reply LS on extending the maximum range for NS values |
Huawei, HiSilicon |
| 7.28.1 |
General and work plan |
|
| R4-2218099 |
Further considerations on extending the maximum range for NS values |
Apple, Charter Communications |
| R4-2218100 |
[draft] Response LS on extending the maximum range for NS values |
Apple, Charter Communications |
| R4-2218101 |
Draft running CR for TR 38.849 |
Apple |
| R4-2218104 |
draft CR: Rolling CR covering the agreed changes from RAN4#104-bis-e |
Apple |
| R4-2218207 |
Discussion on extending the maximum range for NS values |
Mediatek India Technology Pvt. |
| R4-2219082 |
Discussion on non-contiguous UL CA for NR-U |
Nokia, BT plc |
| R4-2220493 |
[draft] Response LS on extending the maximum range for NS values |
Apple, Charter Communications |
| 7.28.2 |
Common requirements (channel raster, A-MPR for 100MHz CBW) |
|
| R4-2218102 |
Channel raster points covering first 20MHz for bands n96 and n102 |
Apple |
| R4-2219704 |
NR-U PC3 MPR |
Skyworks Solutions Inc. |
| R4-2219705 |
NR-U 100MHz A-MPR |
Skyworks Solutions Inc. |
| R4-2220495 |
Way forward for NR-U PC3 MPR/A-MPR |
Charter |
| R4-2220808 |
draft CR: Rolling CR covering the agreed changes from RAN4#104-bis-e |
Apple |
| 7.28.3 |
UE RF requirements for SP and LPI |
|
| R4-2218048 |
Simulation results on UE RF MPR and A-MPR for PC3 |
Charter Communications, Inc |
| R4-2218103 |
NR-U MPR and A-MPR for PC3 |
Apple |
| R4-2218530 |
Discussion on NR-U PC3 UE RF requirements |
LG Electronics |
| R4-2218531 |
Draft running CR on NR-U PC3 A-MPR in South Korea |
LG Electronics |
| R4-2220494 |
Draft running CR on NR-U PC3 A-MPR in South Korea |
LG Electronics |
| R4-2220496 |
WF on remaining topics on NR-U |
Apple |
| 7.28.6 |
Moderator summary and conclusions |
|
| R4-2220100 |
Topic summary for [105][120] NR_unlic_enh |
Moderator (Apple) |
| 8.1 |
Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths |
|
| R4-2218107 |
Remaining issues for the study on licensed spectrum that is not aligned with existing NR channel bandwidths |
Apple |
| 8.1.2 |
SIB1 signaling and CBW configuration |
|
| R4-2218349 |
Discussion on Clarification of channel raster for BS and UE channel bandwidth |
Intel Corporation |
| R4-2218350 |
Clarification of the application of channel raster for BS and UE channel bandwidth [channel-raster] |
Intel Corporation |
| R4-2218351 |
Clarification of the application of channel raster for BS and UE channel bandwidth [channel-raster] |
Intel Corporation |
| R4-2218352 |
Clarification of the application of channel raster for BS and UE channel bandwidth [channel-raster] |
Intel Corporation |
| R4-2218651 |
discussion on channel raster unalignment of n28 |
CMCC |
| R4-2218769 |
UE Channel Bandwidth Configuration |
Qualcomm Incorporated |
| R4-2218825 |
Further background to changes on cell-specific carrier bandwidth signaling and UE specific CHBW configuration in RAN4 specifications |
Ericsson |
| R4-2219047 |
Discussion on SIB1 signaling and CBW configuration |
ZTE Corporation |
| R4-2219142 |
Further discussion on SIB1 signaling and CBW configuration |
Huawei, HiSilicon |
| R4-2219143 |
Consideration of the outcome on SIB1 and CBW configuration issue |
Huawei, HiSilicon |
| R4-2219706 |
Discussion on contentious issues of SIB1 signalling and CBW configuration |
Nokia, Nokia Shanghai Bell |
| R4-2220502 |
WF on irregular channel bandwidth |
Nokia |
| 8.1.3 |
Moderator summary and conclusions |
|
| R4-2220103 |
Topic summary for [105][123] FS_NR_eff_BW_util |
Moderator (Ericsson) |
| 8.2.1 |
General and TR |
|
| R4-2218418 |
TR 38.872 v0.3.0 |
CATT |
| R4-2218737 |
Amendment of the requirement on TX power management |
Sony, Ericsson |
| 8.2.2 |
CA band combination of CA_n5-n8 |
|
| R4-2218367 |
TP for TR 38.872 on CA_n5-n8 architectures |
Apple |
| R4-2219870 |
Considerations on CA_n5-n8 |
Qualcomm Finland RFFE Oy |
| R4-2220504 |
TP for TR 38.872 on CA_n5-n8 architectures |
Apple |
| 8.2.2.1 |
Feasibility investigation of simultaneous reception and transmissions |
|
| R4-2218128 |
CA_n5-n8 feasibility discussion |
Murata Manufacturing Co Ltd. |
| R4-2218294 |
Non-simultaneous Rx/Tx between n5 DL and n8 UL |
Nokia, Nokia Shanghai Bell |
| R4-2218388 |
Blocking and de-sense issues with n8 UL for CA_n5-n8 in both 1UL and 2UL configurations |
Skyworks Solutions Inc. |
| R4-2218484 |
Discussion of the solutions for CA_n5-n8 |
CATT |
| R4-2218865 |
Further discussion on feasibility aspects and RF requirements impact for CA_n5-n8 |
vivo |
| R4-2219205 |
Feasible on CA band combination of n5-n8 |
ZTE Corporation |
| R4-2219259 |
Discussion on CA_n5-n8 |
Xiaomi |
| R4-2219621 |
Discussion on RF architecture and potential solutions for CA_n5-n8 |
Huawei, HiSilicon |
| 8.2.2.2 |
UE RF requirements |
|
| R4-2219262 |
TP on CA_n5-n8 |
Xiaomi |
| R4-2219622 |
TP for TR 38.872 to capture the RF architecture assumption for CA_n5-n8 |
Huawei, HiSilicon |
| 8.2.3 |
CA band combination of CA_n5-n28 |
|
| R4-2218114 |
On CA_n5-n8 architectures |
Apple |
| R4-2218368 |
TP for TR 38.872 on CA_n5-n28 architectures |
Apple |
| R4-2219873 |
Considerations on CA_n5-n28 |
Qualcomm Finland RFFE Oy |
| 8.2.3.1 |
Feasibility investigation of simultaneous reception and transmissions |
|
| R4-2218387 |
MSD due to 2UL configuration for CA_n5-n28 |
Skyworks Solutions Inc. |
| R4-2218866 |
Further discussion on feasibility aspects and RF requirements impact for CA_n5-n28 |
vivo |
| R4-2219260 |
Discussion on CA_n5-n28 |
Xiaomi |
| R4-2219617 |
Discussion on RF architecture and IMD evaluation for CA_n5-n28 |
Huawei, HiSilicon |
| 8.2.3.2 |
UE RF requirements |
|
| R4-2218129 |
CA_n5-n28 MSD due to 2 UL and feasibility |
Murata Manufacturing Co Ltd. |
| R4-2219206 |
TP to TR38.872: TIB,c and RIB,c values for n5-n28 |
ZTE Corporation |
| R4-2219263 |
TP on CA_n5-n28 |
Xiaomi |
| R4-2219618 |
TP for TR 38.872 to capture the RF architecture assumption and IMD evaluation for CA_n5-n28 |
Huawei, HiSilicon |
| R4-2220505 |
TP on CA_n5-n28 |
Xiaomi |
| 8.2.4 |
CA band combination of CA_n8-n20-n28 |
|
| R4-2218115 |
On CA_n8-n20-n28 architectures |
Apple |
| R4-2218369 |
TP for TR 38.872 on CA_n8-n20-n28 architectures |
Apple |
| R4-2219874 |
Considerations on CA_n8-n20-n28 |
Qualcomm Finland RFFE Oy |
| 8.2.4.1 |
Feasibility investigation of simultaneous reception and transmissions |
|
| R4-2218867 |
Further discussion on feasibility aspects and RF requirements impact for CA_n8-n20-n28 |
vivo |
| R4-2219261 |
Discussion on CA_n8-n20-n28 |
Xiaomi |
| 8.2.4.2 |
UE RF requirements |
|
| R4-2218130 |
CA_n8-20-n28 Architecture and MSD due to IMD |
Murata Manufacturing Co Ltd. |
| R4-2219264 |
TP on CA_n8-n20-n28 |
Xiaomi |
| R4-2219619 |
Discussion on RF architecture and IMD evaluation for CA_n8-n20-n28 |
Huawei, HiSilicon |
| R4-2219620 |
TP for TR 38.872 to capture the RF architecture assumption and IMD evaluation for CA_n8-n20-n28 |
Huawei, HiSilicon |
| R4-2220506 |
TP for TR 38.872 to capture the RF architecture assumption and IMD evaluation for CA_n8-n20-n28 |
Huawei, HiSilicon |
| 8.2.5 |
Moderator summary and conclusions |
|
| R4-2220104 |
Topic summary for [105][124] FS_NR_700800900 |
Moderator (CATT) |
| R4-2220507 |
WF on UE architecture and other aspects for CA_n5-n8 |
Qualcomm |
| R4-2220508 |
WF on UE architecture and other aspects for CA_n5-n28 |
Vivo |
| R4-2220509 |
WF on UE architecture and other aspects for CA_n8-n20-n28 |
Murata |
| R4-2220809 |
WF on UE architecture and other aspects for CA_n8-n20-n28 |
Murata |
| 8.3.1 |
General and work plan |
|
| R4-2219762 |
TR 38.846 v0.2.0_Study on simplification of band combination specification for NR and LTE |
ZTE Corporation |
| 8.3.2 |
Simplification of working procedure |
|
| R4-2219080 |
On simplification of band combination working procedure for NR and LTE |
Nokia, Nokia Shanghai Bell |
| 8.3.3 |
Simplification of specification and reduction of test burden |
|
| R4-2218116 |
On FR1 2UL inter-band CA coexistence requirements |
Apple |
| R4-2218267 |
Ue to UE co-ex requriement for band combinations. |
Nokia |
| R4-2219623 |
Discussion on REFSENS test burden reduction |
Huawei, HiSilicon |
| R4-2219624 |
TP for TR 38.846 to capture some agreements for REFSENS test burden reduction |
Huawei, HiSilicon |
| R4-2219699 |
MSD test point simplification for EN-DC |
Skyworks Solutions Inc. |
| R4-2219760 |
TP for TR 38.846 on test burden reduction for multiple MSD in band combinations |
ZTE Corporation |
| R4-2220510 |
TP for TR 38.846 to capture some agreements for REFSENS test burden reduction |
Huawei, HiSilicon |
| R4-2220511 |
TP for TR 38.846 on test burden reduction for multiple MSD in band combinations |
ZTE Corporation |
| 8.3.4 |
Others |
|
| R4-2219625 |
Discussion on the fallback rules for exceptional cases |
Huawei, HiSilicon |
| R4-2219626 |
TP for TR 38.846 to capture the fallback rules with exceptional cases |
Huawei, HiSilicon |
| R4-2219759 |
TP for TR 38.846 on templates of delta TIB and RIB for NE-DC and SUL band combinations |
ZTE Corporation |
| R4-2220512 |
TP for TR 38.846 to capture the fallback rules with exceptional cases |
Huawei, HiSilicon |
| 8.3.5 |
Moderator summary and conclusions |
|
| R4-2220105 |
Topic summary for [105][125] FS_SimBC |
Moderator (ZTE) |
| 8.4.1 |
General and work plan |
|
| R4-2219148 |
TR 38.877 v0.1.0 |
Huawei, HiSilicon |
| 8.4.2 |
Investigation of mmWave multi-band BS |
|
| R4-2218324 |
TP to TR 38.877: Requirements of FR2-1 multi-band BS |
Nokia, Nokia Shanghai Bell |
| R4-2218325 |
Feasibility study on FR2 multi-band RIBs |
Nokia, Nokia Shanghai Bell |
| R4-2218467 |
General consideration on mmWave multi-band BS |
CATT |
| R4-2218468 |
TP for TR 38.877: On definition of FR2-1 multi-band BS in clause 6.1 |
CATT |
| R4-2218771 |
Feasibility of FR2-1 multi-band BS |
Murata Manufacturing Co Ltd. |
| R4-2219149 |
Further discussion of mmWave multi-band BS antenna array |
Huawei, HiSilicon |
| R4-2219150 |
TP for definition of FR2 multi-band BS |
Huawei, HiSilicon |
| R4-2219151 |
On Frequency ranges/groups |
Huawei, HiSilicon |
| R4-2219152 |
TP on RF front end |
Huawei, HiSilicon |
| R4-2219153 |
TP on Antenna array capability |
Huawei, HiSilicon |
| R4-2219154 |
Further discussion on phase shifters |
Huawei, HiSilicon |
| R4-2219155 |
TP on MB RIB requirements |
Huawei, HiSilicon |
| R4-2219373 |
Further discussion on FR2 multi-band operation |
ZTE Corporation |
| R4-2219642 |
TP to TR 38.877: NR mm wave BS |
Ericsson |
| R4-2220294 |
TP to TR 38.877: Requirements of FR2-1 multi-band BS |
Nokia, Nokia Shanghai Bell |
| R4-2220295 |
TP for TR 38.877: On definition of FR2-1 multi-band BS in clause 6.1 |
CATT, Huawei |
| 8.4.3 |
Moderator summary and conclusions |
|
| R4-2220133 |
Summary for [105][307] FS_NR_BS_RF_evo |
Moderator (Huawei) |
| R4-2220249 |
WF for the feasibility study on FR2 multi-band RIB |
Huawei |
| 8.5.1 |
General and work plan |
|
| R4-2219140 |
3GPP TR 38.871 V0.0.2 |
Qualcomm Incorporated |
| 8.5.2 |
Test methods for RF/RRM/Demodulation requirements |
|
| R4-2218109 |
On multi-Rx DL test methodology |
Apple |
| R4-2218215 |
Views on FR2-1 RF OTA test for a device with multi-panel reception (3) |
Anritsu Corporation |
| R4-2218304 |
Discussion on FR2 methods for UEs with multi-Rx |
ROHDE & SCHWARZ |
| R4-2218560 |
Discussion on test setup for 2AoA RF test |
Samsung |
| R4-2218854 |
Discussion on FR2 OTA test methods for multi-Rx |
vivo |
| R4-2219139 |
Discussions on test method for FR2 multi-Rx UE |
Qualcomm Incorporated |
| R4-2219386 |
Discussion on Test methods |
Huawei,HiSilicon |
| R4-2219601 |
On test setup for multi-panel DL reception |
OPPO |
| R4-2219681 |
on the FR2 OTA Test method |
Xiaomi |
| R4-2219851 |
Testing Considerations for Multi AoA Rx Testing |
Keysight Technologies UK Ltd |
| R4-2219884 |
Discussion on Test Setup for Multi-Rx |
CAICT, SAICT |
| 8.5.3 |
Test uncertainty assessments |
|
| R4-2219385 |
Discussion on Measurement uncertainty |
Huawei,HiSilicon |
| 8.5.4 |
Moderator summary and conclusions |
|
| R4-2220155 |
Summary for [105][329] FS_NR_FR2_OTA_enh |
Moderator (Qualcomm) |
| R4-2220264 |
WF for FR2 OTA test SI |
Qualcomm |
| 8.6.2 |
4Tx UE RF requirements |
|
| R4-2218194 |
4 Tx RF issues |
Qualcomm Technologies Int |
| R4-2218529 |
Discussion on 4Tx UE RF requirements |
LG Electronics |
| R4-2218548 |
Power Class fallback aspect |
Nokia, Nokia Shanghai Bell |
| R4-2218860 |
Further discussion on 4Tx UE RF requirements |
vivo |
| R4-2219035 |
Discussion on 4Tx on for CPE FWA vehicle industrial devices |
Xiaomi |
| R4-2219207 |
Further discussion on 4Tx UE RF requirements |
ZTE Corporation |
| R4-2219567 |
On 4Tx UE RF requirements |
Huawei, HiSilicon |
| R4-2219592 |
R18 Discussion on 4Tx FWA |
OPPO |
| R4-2219992 |
EVM for Transmit Diversity with 4Tx |
Lenovo |
| R4-2219993 |
EVM for 4x4 UL MIMO |
Lenovo |
| R4-2220515 |
WF on 4Tx requirements |
Vivo |
| R4-2220830 |
WF on 4Tx requirements |
Vivo |
| 8.6.3 |
8Rx UE RF requirements |
|
| R4-2218209 |
Discussion on FR1 8RX UE RF requirements |
Mediatek India Technology Pvt. |
| R4-2218549 |
On antenna virtualization and reporting delta TRxSRS |
Nokia, Nokia Shanghai Bell |
| R4-2218752 |
Views on 8Rx for Rel-18 RF FR1 enhancements |
Sony |
| R4-2219036 |
Discussion on 8Rx on for CPE FWA vehicle industrial devices |
Xiaomi |
| R4-2219494 |
draft CR for 38.101-1 removal of 3dB relaxation to PCMAX_H,f,c for 8Rx capable UE |
Huawei, HiSilicon |
| R4-2219495 |
draft LS on the UE SRS IL imbalance issue |
Huawei, HiSilicon |
| R4-2219496 |
On FR1 8Rx UE RF requirements |
Huawei, HiSilicon |
| R4-2219591 |
R18 Discussion on 8Rx FWA |
OPPO |
| R4-2219875 |
8RX UE RF requirements |
Qualcomm Finland RFFE Oy |
| R4-2220020 |
Further view on 8Rx for Rel-18 RF FR1 enhancements |
NTT DOCOMO INC. |
| R4-2220033 |
Discussion on UE RF requirements for 8Rx in FR1 |
Ericsson Limited |
| R4-2220516 |
WF on 8Rx RF requirements |
NTT DOCOMO, INC. |
| 8.6.4 |
Lower MSD for inter-band CA/EN-DC/DC combinations |
|
| R4-2218553 |
TP for TR 38.881 possible Lower MSD signaling approaches |
Nokia, Nokia Shanghai Bell |
| R4-2219568 |
TR 38.881 v0.2.0 |
Huawei, HiSilicon |
| R4-2220514 |
WF on study of lower MSD |
Huawei, HiSilicon |
| R4-2220824 |
WF on study of lower MSD |
Huawei, HiSilicon |
| 8.6.4.1 |
Study of approach to Improve MSD |
|
| R4-2218297 |
On MSD evaluation with new assumptions for MSD improvement |
Facebook Japan K.K. |
| R4-2218555 |
Power Class aspect on lower MSD |
Nokia, Nokia Shanghai Bell |
| R4-2218858 |
Further analysis on improve MSD |
vivo |
| R4-2219037 |
Discussion on lower MSD for inter-band CA/EN-DC/DC |
Xiaomi |
| R4-2219569 |
TP for TR 38.881 Feasibility study from companies and conclusion for lower MSD improvement |
Huawei, HiSilicon |
| R4-2219593 |
R18 Discussion on MSD improvement study |
OPPO |
| R4-2220513 |
TP for TR 38.881 Feasibility study from companies and conclusion for lower MSD improvement |
Huawei, HiSilicon |
| 8.6.4.2 |
Study of signaling for improved lower MSD |
|
| R4-2218117 |
Views on signaling for lower MSD |
Apple |
| R4-2218195 |
Signalling for low MSD |
Qualcomm Technologies Int |
| R4-2218298 |
On lower MSD capability signaling |
Facebook Japan K.K. |
| R4-2218554 |
Lower MSD capability signaling |
Nokia, Nokia Shanghai Bell |
| R4-2218606 |
Further discussion on the capability signalling design for Low MSD indication |
CHTTL |
| R4-2218647 |
Discussion on lower MSD capability |
CMCC |
| R4-2218674 |
Discussion on signaling for improved lower MSD |
LG Electronics France |
| R4-2218756 |
Discussion on signaling for Lower MSD |
Samsung |
| R4-2218840 |
Continue discussion for low MSD signalling study |
MediaTek Inc. |
| R4-2218859 |
Further study of signaling on Lower MSD |
vivo |
| R4-2219038 |
Discussion on lower MSD signaling for inter-band CA/EN-DC/DC |
Xiaomi |
| R4-2219269 |
On the signalling design for lower MSD capability |
Huawei, HiSilicon |
| R4-2219594 |
R18 Discussion on MSD improvement signalling |
OPPO |
| 8.6.6.1 |
8Rx UE demodulation and CSI |
|
| R4-2218063 |
Views on 8Rx demodulation performance requirements |
Qualcomm India Pvt Ltd |
| R4-2218314 |
UE demodulation and CSI reporting requirements for 8 Rx in FR1 |
Ericsson |
| R4-2218315 |
Initial simulation results for 8Rx PDSCH demodulation in FR1 |
Ericsson |
| R4-2218941 |
Views on 8Rx demodulation performance requirements |
Qualcomm India Pvt Ltd |
| R4-2219007 |
Views on 8Rx UE demodulation performance requirements |
NTT DOCOMO, INC. |
| R4-2219046 |
Discussion on 8Rx UE demodulation and CSI |
ZTE Corporation |
| R4-2219515 |
Discussion on UE demodulation and CSI requirements for 8RX |
Huawei, HiSilicon |
| R4-2219728 |
Discussion on 8Rx UE demodulation and CSI requirements |
Nokia, Nokia Shanghai Bell |
| R4-2219769 |
Views on 8Rx UE Requirements |
MediaTek inc. |
| 8.6.7 |
Moderator summary and conclusions |
|
| R4-2220060 |
Topic summary for [105][214] NR_ENDC_ RF_FR1_enh2_RRM |
Moderator (NTT DoCoMo) |
| R4-2220106 |
Topic summary for [105][126] FR1_enh2_part1 |
Moderator (Huawei) |
| R4-2220107 |
Topic summary for 105][127] FR1_enh2_part2 |
Moderator (Vivo) |
| R4-2220108 |
Topic summary for [105][128] FR1_enh2_part3 |
Moderator (NTT Docomo) |
| R4-2220152 |
Summary for [105][326] RF_FR1_enh2_Demod |
Moderator (Huawei) |
| R4-2220274 |
WF for 8Rx UE demodulation and CSI requirements |
Huawei |
| R4-2220613 |
WF for 8Rx UE demodulation and CSI requirements |
Huawei |
| 8.7.1 |
General and work plan |
|
| R4-2219121 |
TR38.891 v 0.2.0 for NR RF requirements enhancement for frequency range 2 (FR2), Phase 3 |
Xiaomi,Nokia |
| 8.7.2 |
UL 256QAM |
|
| R4-2218040 |
On enabling FR2 UL256QAM |
Qualcomm Incorporated |
| R4-2218326 |
Link level simulation results for FR2-1 UL 256QAM |
Nokia, Nokia Shanghai Bell |
| R4-2218327 |
System level simulation results for FR2-1 UL 256QAM |
Nokia, Nokia Shanghai Bell |
| R4-2218328 |
Proposals on UE RF requirements for FR2-1 UL 256QAM |
Nokia, Nokia Shanghai Bell |
| R4-2218595 |
Discussion on FR2 UL 256QAM |
ZTE Corporation |
| R4-2218681 |
Discussion on FR2-1 UL 256QAM |
LG Electronics France |
| R4-2218753 |
UL 256-QAM simulations for FR2-1 |
Sony |
| R4-2218869 |
Further evaluation for FR2-1 UL 256QAM based on SLS |
vivo |
| R4-2218940 |
Discussion on EVM requirements for FR2-1 UL 256QAM |
MediaTek Korea Inc. |
| R4-2219075 |
Discussion on UL 256QAM |
Beijing Xiaomi Software Tech |
| R4-2219122 |
TP for TR 38.891 on link level simulation results and system level simulation assumption for FR2 UL 256QAM |
Xiaomi |
| R4-2219144 |
Simulation results for UL 256QAM |
Huawei, HiSilicon |
| R4-2220036 |
Simulation results for UL 256QAM feasibility study for FR2-1 |
Ericsson Limited |
| R4-2220535 |
WF on FR2 UL 256QAM |
Xiaomi |
| R4-2220810 |
WF on FR2 UL 256QAM |
Xiaomi |
| 8.7.3 |
Beam correspondence requirements for RRC_INACTIVE and initial access |
|
| R4-2218692 |
LS on beam lock function for BC testing in initial access |
Apple |
| R4-2218754 |
Views on Beam correspondence for initial access |
Sony, Ericsson |
| R4-2220517 |
WF on beam correspondence requirements for initial access and RRC_inactive mode |
Nokia |
| 8.7.3.1 |
Beam correspondence requirement applicability |
|
| R4-2218041 |
On initial access beam correspondence |
Qualcomm Incorporated |
| R4-2218299 |
Beam correspondence requirement applicability |
Nokia, Nokia Shanghai Bell |
| R4-2218558 |
FR2 beam correspondence requirement for initial access |
Samsung |
| R4-2218637 |
beam correspondence requirement for initial access state |
CMCC |
| R4-2218689 |
Further consideration on BC requirement applicability for IA/RA-SDT/CG-SDT |
Apple |
| R4-2218870 |
Discussion on beam correspondence requirement applicability |
vivo |
| R4-2219115 |
Discussion on beam correspondence requirements for RRC_INACTIVE and initial access |
Beijing Xiaomi Software Tech |
| R4-2219189 |
Discussion on beam correspondence requirement and its applicability |
ZTE Corporation |
| R4-2219596 |
R18 Discussion on FR2 beam correspondence requirements in IA |
OPPO |
| R4-2219815 |
On beam correspondence requirements applicability |
Huawei, HiSilicon |
| R4-2219900 |
On beam correspondence requirements for RRC_INACTIVE and initial access |
MediaTek |
| 8.7.3.2 |
UE beam type and DRX implications |
|
| R4-2218300 |
UE beam type and DRX implications |
Nokia, Nokia Shanghai Bell |
| R4-2218690 |
Further consideration on UE beam type and DRX implications for BC |
Apple |
| R4-2218871 |
Discussion on beam type and implementation agnostic |
vivo |
| R4-2219123 |
Discussion on beam type and DRX implication |
Xiaomi |
| R4-2219597 |
R18 Discussion on FR2 beam type in IA |
OPPO |
| R4-2219816 |
On UE beam Type for Rel-18 Inactive Beam Correspondence |
Huawei, HiSilicon |
| R4-2219901 |
On beam type for RRC_INACTIVE and initial access |
MediaTek |
| 8.7.3.3 |
Beam correspondence test issues |
|
| R4-2218301 |
Beam Correspondence Test Issues |
Nokia, Nokia Shanghai Bell |
| R4-2218559 |
FR2 beam correspondence test for initial access |
Samsung |
| R4-2218638 |
beam correspondence test issues for initial access state |
CMCC |
| R4-2218691 |
Further consideration on test issue for beam correspondence |
Apple |
| R4-2218872 |
Discussion on beam correspondence test issues |
vivo |
| R4-2219598 |
R18 Discussion on FR2 beam correspondence test in IA |
OPPO |
| R4-2219817 |
On beam correspondence test issues |
Huawei, HiSilicon |
| R4-2219902 |
On beam correspondence requirements test issues for RRC_INACTIVE and initial access |
MediaTek |
| R4-2220518 |
LS on testability for BC testing in initial access |
Apple, Mediatek |
| R4-2220825 |
LS on testability for BC testing in initial access |
Apple, Mediatek |
| 8.7.4 |
Moderator summary and conclusions |
|
| R4-2220109 |
Topic summary for [105][129] FR2_enh_req_Ph3_part1 |
Moderator (Nokia) |
| R4-2220110 |
Topic summary for [105][130] FR2_enh_req_Ph3_part2 |
Moderator (Xiaomi) |
| 8.8.2 |
UE RF requirements for simultaneous DL reception with up to 4 layer MIMO |
|
| R4-2218755 |
Further views on multi-Rx chain DL reception in FR2 |
Sony, Ericsson |
| R4-2219497 |
On UE RF requirement for FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| 8.8.2.1 |
System parameter assumption, UE architecture and conditions of UE RF requirements |
|
| R4-2218043 |
On specifying requirements for mDCI UEs |
Qualcomm Incorporated |
| R4-2218165 |
System parameter and UE assumption for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2218329 |
Proposal on UE RF System parameter assumption, UE architecture and conditions of UE RF requirements for FR2-1 multi-Rx chain DL reception |
Nokia, Nokia Shanghai Bell |
| R4-2218556 |
System and UE assumptions for FR2 simultaneous DL reception from different directions |
Samsung |
| R4-2218873 |
Further consideration on system parameter of multi-Rx DL reception |
vivo |
| R4-2219124 |
Discussion on UE RF system assumption supporting simultaneous DL reception |
Xiaomi |
| R4-2219192 |
Discussion on System parameter and UE architecture of UE RF requirements |
ZTE Corporation |
| R4-2219852 |
System Parameter Assumptions for Multi AoA Rx Testing |
Keysight Technologies UK Ltd |
| R4-2219868 |
Discussion on RF test methods for UEs with multi-Rx |
ROHDE & SCHWARZ |
| R4-2220529 |
Discussion on System parameter and UE architecture of UE RF requirements |
ZTE Corporation |
| R4-2220533 |
WF on UE RF requirements for FR2_multiRx_UERF |
Apple |
| 8.8.2.2 |
UE RF requirements |
|
| R4-2218042 |
On UE RF requirements for 2AoA FR2 DL MIMO |
Qualcomm Incorporated |
| R4-2218166 |
RF requirement for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2218330 |
Proposal on UE RF requirements for FR2-1 multi-Rx chain DL reception |
Nokia, Nokia Shanghai Bell |
| R4-2218528 |
Discussion on UE RF requirements for simultaneous DL reception |
LG Electronics |
| R4-2218557 |
RF requirements for FR2 simultaneous DL reception from different directions |
Samsung |
| R4-2218874 |
Discussion on RF requirement for multi-Rx DL reception |
vivo |
| R4-2219125 |
Discussion on UE RF requirements supporting simultaneous DL reception |
Xiaomi |
| R4-2219193 |
Discussion on UE RF requirements for simultaneous DL reception |
ZTE Corporation |
| R4-2219600 |
Consideration on small AoA angular separation |
OPPO |
| R4-2220017 |
Complexity Reduction for Multi-Rx Multi-AOA Coverage Evaluation |
Lenovo |
| R4-2220530 |
Discussion on UE RF requirements for simultaneous DL reception |
ZTE Corporation |
| 8.8.3.1 |
Analysis of scope and scenarios |
|
| R4-2218335 |
Discussion on FR2 multi Rx chain scope and scenarios |
Intel Corporation |
| R4-2218393 |
Discussion on scope and scenarios for FR2 multi-Rx chain DL reception |
CMCC |
| R4-2218408 |
Analysis of scope and scenarios |
Qualcomm Incorporated |
| R4-2218586 |
on the multi-RX chain scenarios |
Xiaomi |
| R4-2218596 |
Discussion on scope and scenario of RRM for FR2 multi-Rx chains |
LG Electronics Inc. |
| R4-2218738 |
Discussion on simultaneous DL reception from different directions for scope and scenarios |
MediaTek Inc. |
| R4-2218775 |
On scope and scenarios for FR2 multi-Rx |
vivo |
| R4-2218977 |
On scope and scenarios for FR2_multiRX_DL |
OPPO |
| R4-2219008 |
Scope and scenarios for FR2 multi Rx chain DL reception |
NTT DOCOMO, INC. |
| R4-2219250 |
Discussion on scope and scenarios for R18 FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| R4-2219290 |
Discussion on scope and general scenarios for FR2 multi-RX |
Samsung |
| R4-2219434 |
Discussion on scope and scenarios for simultaneous DL reception from different directions |
ZTE Corporation |
| R4-2219739 |
Discussion on scope and scenarios for the requirements for multi-RX RRM |
Nokia, Nokia Shanghai Bell |
| R4-2219946 |
Discussion on scope and UE capabilities |
Ericsson |
| R4-2220370 |
Ad-hoc meeting minutes: Rel-18 NR FR2 multi-Rx chain DL reception WI |
Qualcomm |
| R4-2220400 |
WF on NR FR2 multi-Rx chain DL reception – Part 1 |
Vivo |
| R4-2220401 |
WF on NR FR2 multi-Rx chain DL reception – Part 2 |
Qualcomm |
| R4-2220402 |
WF on NR FR2 multi-Rx chain DL reception – Part 3 |
Ericsson |
| R4-2220732 |
WF on NR FR2 multi-Rx chain DL reception – Part 1 |
Vivo |
| R4-2220742 |
WF on NR FR2 multi-Rx chain DL reception – Part 1 |
Vivo |
| R4-2220743 |
WF on NR FR2 multi-Rx chain DL reception – Part 2 |
Qualcomm |
| 8.8.3.2 |
Analysis of general aspects |
|
| R4-2218167 |
General aspects for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2218336 |
Discussion on FR2 multi Rx chain general aspects |
Intel Corporation |
| R4-2218409 |
Analysis of general aspects |
Qualcomm Incorporated |
| R4-2218587 |
on the multi-RX chain general aspects |
Xiaomi |
| R4-2218597 |
Discussion on general aspects of RRM for FR2 multi-Rx chains |
LG Electronics Inc. |
| R4-2218739 |
Discussion on simultaneous DL reception from different directions for general aspects |
MediaTek Inc. |
| R4-2218776 |
On general aspects for FR2 multi-Rx |
vivo |
| R4-2218978 |
On general requirements for FR2_multiRX_DL |
OPPO |
| R4-2219009 |
General aspects discussions for FR2 multi Rx chain DL reception |
NTT DOCOMO, INC. |
| R4-2219251 |
Discussion on RRM general aspects for R18 FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| R4-2219291 |
Analysis on general aspects for FR2 multi-RX |
Samsung |
| R4-2219435 |
Discussion on general aspects on RRM requirements for simultaneous DL reception from different directions |
ZTE Corporation |
| R4-2219740 |
Discussion on general aspects for multi Rx DL |
Nokia, Nokia Shanghai Bell |
| R4-2219947 |
Discussion on general aspects |
Ericsson |
| 8.8.3.3 |
L3 measurement specifically related |
|
| R4-2218168 |
On L3 measurements for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2218337 |
Discussion on RRM impacts for L1 measurement based on FR2 multi Rx chain |
Intel Corporation |
| R4-2218394 |
Discussion on L3 measurement for FR2 multi-Rx chain DL reception |
CMCC |
| R4-2218410 |
L3 measurement specifically related |
Qualcomm Incorporated |
| R4-2218588 |
on the multi-RX chain L3 measurement |
Xiaomi |
| R4-2218598 |
Discussion on L3 measurement related for RRM for FR2 multi-Rx chains |
LG Electronics Inc. |
| R4-2218740 |
Discussion on simultaneous DL reception from different directions for L3 measurement |
MediaTek Inc. |
| R4-2218777 |
On L3 measurement for multi-Rx |
vivo |
| R4-2218979 |
Discussion on L3 requirements for FR2_multiRX_DL |
OPPO |
| R4-2219010 |
Discussions for L3 measurements on FR2 multi Rx chain DL reception |
NTT DOCOMO, INC. |
| R4-2219252 |
Discussion on L3 measurement impacts for R18 FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| R4-2219436 |
Discussion on L3 measurement related aspects for simultaneous DL reception from different directions |
ZTE Corporation |
| R4-2219741 |
Discussion on RRM L3 enhancements for multi Rx DL in FR2 |
Nokia, Nokia Shanghai Bell |
| R4-2219948 |
Discussion on L3 measurements and procedures |
Ericsson |
| 8.8.3.4 |
L1 measurement specifically related |
|
| R4-2218169 |
On L1 measurements for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2218589 |
on the multi-RX chain L1 measurement |
Xiaomi |
| R4-2218599 |
Discussion on L1 measurement related for RRM for FR2 multi-Rx chains |
LG Electronics Inc. |
| R4-2218741 |
Discussion on simultaneous DL reception from different directions for L1 measurement |
MediaTek Inc. |
| R4-2218778 |
On L1 measurement for multi-Rx |
vivo |
| R4-2218980 |
Discussion on L1 requirements for FR2_multiRX_DL |
OPPO |
| R4-2219011 |
Discussions for L1 measurements on FR2 multi Rx chain DL reception |
NTT DOCOMO, INC. |
| R4-2219253 |
Discussion on L1 measurement impacts for R18 FR2 multi-Rx chain DL reception |
Huawei, HiSilicon |
| R4-2219742 |
Discussion on RRM L1 enhancements for multi Rx DL in FR2 |
Nokia, Nokia Shanghai Bell |
| R4-2219949 |
Discussion on L1 measurements and procedures |
Ericsson |
| 8.8.3.5 |
TCI state switching requirements |
|
| R4-2218170 |
TCI state switching for NR FR2 multi-Rx chain DL reception |
Apple |
| R4-2218590 |
on the multi-RX chain TCI state switching |
Xiaomi |
| R4-2218742 |
Discussion on simultaneous DL reception from different directions for TCI state switching |
MediaTek Inc. |
| R4-2218779 |
On TCI state switching for multi-Rx |
vivo |
| R4-2218981 |
Discussion on TCI state switching for FR2_multiRX_DL |
OPPO |
| R4-2219242 |
Discussion RRM requirements of TCI state switching for multi-Rx |
Huawei, HiSilicon |
| R4-2219743 |
Discussion on TCI state switching requirements for multi Rx DL in FR2 |
Nokia, Nokia Shanghai Bell |
| R4-2219950 |
Discussion on active TCI state requirements |
Ericsson |
| 8.8.4 |
Moderator summary and conclusions |
|
| R4-2220061 |
Topic summary for [105][215] FR2_multiRx_RRM_part1 |
Moderator (Vivo) |
| R4-2220062 |
Topic summary for [105][216] FR2_multiRx_RRM_part2 |
Moderator (Qualcomm) |
| R4-2220063 |
Topic summary for [105][217] FR2_multiRx_RRM_part3 |
Moderator (Ericsson) |
| R4-2220111 |
Topic summary for [105][131] FR2_multiRx_UERF_part1 |
Moderator (Qualcomm) |
| R4-2220112 |
Topic summary for [105][132] FR2_multiRx_UERF_part2 |
Moderator (Apple) |
| 8.9.2.1 |
L3 part enhancement for FR2 SCell activation |
|
| R4-2218140 |
On L3 part enhancement for FR2 SCell activation |
Apple |
| R4-2218333 |
Discussion on L3 part enhancement for FR2 SCell activation |
Intel Corporation |
| R4-2218396 |
Discussion on L3 part enhancement for FR2 SCell activation |
CMCC |
| R4-2218540 |
Remaining issues on RRM requirements about FR2 unknown Scell activation enhancements L3 part |
Qualcomm Incorporated |
| R4-2218545 |
Discussion on L3 part enhancement for FR2 SCell activation |
China Telecom |
| R4-2218565 |
Discussion on L3 part enhancement for FR2 SCell activation |
Xiaomi |
| R4-2218593 |
Discussion on L3 enhancement for FR2 SCell activation delay reduction |
LG Electronics Inc. |
| R4-2218678 |
L3 part enhancement on FR2 SCell activation delay reduction |
Nokia, Nokia Shanghai Bell |
| R4-2218982 |
Discussion on L3 part enhancement for FR2 Scell activation delay reduction |
OPPO |
| R4-2219177 |
Discussion on L3 aspects of FR2 SCell activation enhancements |
vivo |
| R4-2219233 |
Discussion on L3 enhancement for FR2 SCell activation delay reduction |
Huawei, HiSilicon |
| R4-2219438 |
Discussion on the L3 part enhancement of RRM requirements for FR2 SCell activation delay reduction |
ZTE Corporation |
| R4-2219919 |
Discussion on L3 part enhancement for FR2 SCell activation |
MediaTek inc. |
| R4-2219951 |
Discussion on L3 part enhancement for FR2 SCell activation |
Ericsson |
| R4-2220411 |
Ad-hoc meeting minutes: Rel-18 Even Further RRM enhancement for NR and MR-DC WI |
Apple |
| R4-2220440 |
WF on Even Further RRM enhancement for NR and MR-DC – Part 1 |
Apple |
| R4-2220442 |
WF on Even Further RRM enhancement for NR and MR-DC – Part 2 |
OPPO |
| R4-2220736 |
WF on Even Further RRM enhancement for NR and MR-DC – Part 2 |
OPPO |
| 8.9.2.2 |
L1 part enhancement for FR2 SCell activation |
|
| R4-2218141 |
On L1 part enhancement for FR2 SCell activation |
Apple |
| R4-2218334 |
Discussion on L1 part enhancement for FR2 SCell activation |
Intel Corporation |
| R4-2218395 |
Discussion on L1 part enhancement for FR2 SCell activation |
CMCC |
| R4-2218541 |
Remaining issues on RRM requirements about FR2 unknown Scell activation enhancements L1 part |
Qualcomm Incorporated |
| R4-2218546 |
Discussion on L1 part enhancement for FR2 SCell activation |
China Telecom |
| R4-2218566 |
Discussion on L1 part enhancement for FR2 SCell activation |
Xiaomi |
| R4-2218594 |
Discussion on L1 enhancement for FR2 SCell activation delay reduction |
LG Electronics Inc. |
| R4-2218679 |
L1 part enhancement on FR2 SCell activation delay reduction |
Nokia, Nokia Shanghai Bell |
| R4-2218983 |
Discussion on L1 part enhancement for FR2 Scell activation delay reduction |
OPPO |
| R4-2219178 |
Discussion on L1 aspects of FR2 SCell activation enhancements |
vivo |
| R4-2219234 |
Discussion on L1 enhancement for FR2 SCell activation delay reduction |
Huawei, HiSilicon |
| R4-2219439 |
Discussion on the L1 part enhancement of RRM requirements for FR2 SCell activation delay reduction |
ZTE Corporation |
| R4-2219920 |
Discussion on L1 part enhancement for FR2 SCell activation |
MediaTek inc. |
| R4-2219952 |
Discussion on L1 part enhancement for FR2 SCell activation |
Ericsson |
| 8.9.2.3 |
Other potential enhancement for FR2 SCell activation |
|
| R4-2218142 |
On other potential enhancement for FR2 SCell activation |
Apple |
| R4-2218547 |
Discussion on other potential enhancement for FR2 SCell activation |
China Telecom |
| R4-2218680 |
Other enhancements on FR2 SCell activation delay reduction |
Nokia, Nokia Shanghai Bell |
| R4-2219034 |
Discussions on SCell activation requirement with different PCI from serving cell |
NTT DOCOMO, INC. |
| R4-2219235 |
Discussion on FR2 SCell activation delay reduction |
Huawei, HiSilicon |
| R4-2219440 |
Discussion on other aspects of RRM requirements enhancement for FR2 SCell activation delay reduction |
ZTE Corporation |
| R4-2219921 |
Discussion on other potential enhancement for FR2 SCell activation |
MediaTek inc. |
| R4-2219953 |
Discussion on other potential enhancement for FR2 SCell activation |
Ericsson |
| 8.9.3 |
RRM core requirements for FR1-FR1 NR-DC |
|
| R4-2218143 |
On RRM requirements for FR1-FR1 NR-DC |
Apple |
| R4-2218332 |
Discussion on FR1-FR1 NR-DC |
Intel Corporation |
| R4-2218542 |
Remaining issues on RRM requirements about FR1+FR1 NR-DC |
Qualcomm Incorporated |
| R4-2218577 |
Discussion on RRM core requirements for FR1-FR1 NR-DC |
Xiaomi |
| R4-2218686 |
discussion on FR1+FR1 NR-DC |
Nokia, Nokia Shanghai Bell |
| R4-2218743 |
Discussion on R18 RRM for FR1-FR1 NR-DC |
MediaTek Inc. |
| R4-2218797 |
Further discussion on FR1-FR1 NR-DC requirement |
vivo |
| R4-2218984 |
Discussion on RRM requirements for FR1-FR1 NR-DC |
OPPO |
| R4-2219236 |
Discussion RRM requirements for FR1-FR1 NR-DC |
Huawei, HiSilicon |
| R4-2219648 |
Discussion on define RRM requirements for FR1-FR1 NR-DC scenarios |
Ericsson |
| 8.9.4 |
Moderator summary and conclusions |
|
| R4-2220064 |
Topic summary for [105][218] NR_RRM_enh3_part1 |
Moderator (Apple) |
| R4-2220065 |
Topic summary for [105][219] NR_RRM_enh3_part2 |
Moderator (OPPO) |
| 8.10.2 |
RRM core requirements for pre-configured MGs, multiple concurrent MGs and NCSG |
|
| R4-2218515 |
On joint requirements for Rel-17 measurement gap enhancements |
Qualcomm Incorporated |
| 8.10.2.1 |
Scope and general issues |
|
| R4-2218147 |
On R18 gap enhancement scope |
Apple |
| R4-2218344 |
Discussion on using scenarios for pre-configured MGs, multiple concurrent MGs and NCSG |
Intel Corporation |
| R4-2218799 |
On scope and general issues for pre-configured MGs, multiple concurrent MGs and NCSG. |
vivo |
| R4-2219314 |
Discussion on the general issues of PreMG, ConMGs, NCSG |
Ericsson |
| R4-2219744 |
Discussion on general issues for preconfigured and NCSG |
Nokia, Nokia Shanghai Bell |
| R4-2219930 |
Scope and general issues |
MediaTek inc. |
| 8.10.2.2 |
Case 1 requirements (Pre-configured MG and concurrent MG) |
|
| R4-2218148 |
On R18 gap enhancement case 1 requirements |
Apple |
| R4-2218345 |
Discussion on RRM requirements for combinations of pre-configured MGs and multiple concurrent MGs |
Intel Corporation |
| R4-2218392 |
Discussion on Pre-configured MG and concurrent MG |
CMCC |
| R4-2218435 |
Discussion on case 1 requirements for combination of pre-MG and concurrent MGs |
CATT |
| R4-2218567 |
RRM requirements for the combination of Pre-MG and concurrent MG |
Xiaomi |
| R4-2218800 |
On case 1 requirement for pre-configured MGs, multiple concurrent MGs and NCSG |
vivo |
| R4-2218992 |
Discussion on case 1 requirements preMG and conMG |
OPPO |
| R4-2219315 |
Discussion on PreMG and ConMGs |
Ericsson |
| R4-2219427 |
Discussion on Case 1 RRM requirements |
ZTE Corporation |
| R4-2219548 |
Discussion on joint working of pre-MG and con-MG |
Huawei, HiSilicon |
| R4-2219913 |
Discussion on Case 1 requirements |
Nokia, Nokia Shanghai Bell |
| R4-2219931 |
Discussion on case 1 requirements (Pre-configured MG and concurrent MG) |
MediaTek inc. |
| 8.10.2.3 |
Case 2 requirements (NCSG and concurrent MG) |
|
| R4-2218149 |
On R18 gap enhancement case 2 requirements |
Apple |
| R4-2218346 |
Discussion on RRM requirements for combinations of NCSG and multiple concurrent MGs |
Intel Corporation |
| R4-2218391 |
Discussion on NCSG and concurrent MG |
CMCC |
| R4-2218436 |
Discussion on case 2 requirements for combination of NCSG and concurrent MGs |
CATT |
| R4-2218568 |
RRM requirements for the combination of NCSG and concurrent MG |
Xiaomi |
| R4-2218801 |
On case 2 requirements for pre-configured MGs, multiple concurrent MGs and NCSG |
vivo |
| R4-2218993 |
Discussion on case 2 requirements NCSG and conMG |
OPPO |
| R4-2219316 |
Discussion on NCSG and ConMGs |
Ericsson |
| R4-2219428 |
Discussion on Case 2 RRM requirements |
ZTE Corporation |
| R4-2219549 |
Discussion on joint working of NCSG and con-MG |
Huawei, HiSilicon |
| R4-2219914 |
Discussion on Case 2 requirements |
Nokia, Nokia Shanghai Bell |
| R4-2219932 |
Discussion on case 2 requirements (NCSG and concurrent MG) |
MediaTek inc. |
| 8.10.3.1 |
Measurement without gaps for UEs reporting NeedForGapsInfoNR |
|
| R4-2218150 |
On measurement without gaps for UEs reporting NeedForGapsInfoNR |
Apple |
| R4-2218347 |
Discussion on measurements without gaps when UE reporting NFG |
Intel Corporation |
| R4-2218401 |
Discussion on measurements without gaps for UEs reporting NeedForGapsInfoNR |
CMCC |
| R4-2218437 |
Discussion on RRM requirements for measurement without gaps for UEs reporting NeedForGapsInfoNR |
CATT |
| R4-2218543 |
Remaining issues on RRM requirements about Needforgap |
Qualcomm Incorporated |
| R4-2218578 |
Discussion on RRM requirements for measurement without gaps for UEs reporting NeedForGapsInfoNR |
Xiaomi |
| R4-2218802 |
On Measurement without gaps for UEs reporting NeedForGapsInfoNR |
vivo |
| R4-2218994 |
On Measurement without gaps for UEs reporting NeedForGapsInfoNR |
OPPO |
| R4-2219317 |
Discussion on NeedForGaps measurement |
Ericsson |
| R4-2219550 |
Discussion on requirements for NeedForGaps |
Huawei, HiSilicon |
| R4-2219745 |
Discussion on measurements without gaps |
Nokia, Nokia Shanghai Bell |
| R4-2219933 |
Discussion on measurement without gaps for UEs reporting NeedForGapsInfoNR |
MediaTek inc. |
| R4-2220359 |
WF on NR_MG_enh2 Part 1 |
MediaTek |
| R4-2220360 |
WF on NR_MG_enh2 Part 2 |
Intel Corporation |
| 8.10.3.2 |
Inter-RAT measurement without gap |
|
| R4-2218151 |
On R18 inter-RAT measurement without gap |
Apple |
| R4-2218348 |
Discussion on inter-RAT measurement without gaps |
Intel Corporation |
| R4-2218398 |
Discussion on inter-RAT measurements without gaps |
CMCC |
| R4-2218438 |
Discussion on RRM requirements for Inter-RAT measurement without gap |
CATT |
| R4-2218544 |
Remaining issues on RRM requirements abou Inter-RAT measurements without gap |
Qualcomm Incorporated |
| R4-2218579 |
Discussion on RRM requirements for inter-RAT measurement without gap |
Xiaomi |
| R4-2218803 |
On Inter-RAT measurement without gap |
vivo |
| R4-2218995 |
Discussion on RRM requirements for Inter-RAT measurement without gap |
OPPO |
| R4-2219318 |
Discussion on Inter-RAT measurement without gap |
Ericsson |
| R4-2219551 |
Discussion on inter-RAT MG-less measurement |
Huawei, HiSilicon |
| R4-2219746 |
Discussion on inter-RAT measurements without gaps |
Nokia, Nokia Shanghai Bell |
| R4-2219934 |
Discussion on inter-RAT measurements |
MediaTek inc. |
| R4-2220361 |
WF on NR ATG RRM requirements |
CMCC |
| 8.10.4 |
Moderator summary and conclusions |
|
| R4-2220066 |
Topic summary for [105][220] NR_MG_enh2_part1 |
Moderator (MediaTek) |
| R4-2220067 |
Topic summary for [105][221] NR_MG_enh2_part2 |
Moderator (Intel) |
| R4-2220329 |
Ad-hoc meeting minutes: Rel-18 Further enhancements on NR and MR-DC measurement gaps and measurements without gaps WI |
MediaTek |
| 8.11.1 |
General and work plan |
|
| R4-2218192 |
Update on WI scope for Support of intra-band non-collocated EN-DC/NR-CA deployment |
Apple |
| 8.11.2 |
UE RF architecture and RF requirements |
|
| R4-2218193 |
Further discussion on intra-band non-collocated CA/EN-DC |
Apple |
| R4-2218281 |
Intra-band non-collocated EN-DC/NR-CA type 4 UE |
Nokia |
| R4-2218417 |
Type 3 Capability for Non-collocated Intra-band |
Murata Manufacturing Co Ltd. |
| R4-2218526 |
Type 3 architecture aspects for 4Rx non-collocated overlapping bands |
Skyworks Solutions Inc. |
| R4-2218682 |
Draft CR on introducing power imbalance requirement for intra-band non-collocated CA |
Apple |
| R4-2218757 |
Further consideration on Fs assumption for non-collocated EN-DC, NR-CA deployment |
Samsung |
| R4-2218758 |
LS to RAN2 on intraBandFreqSeparationUL-AggBW-GapBW-r16 |
Samsung |
| R4-2218770 |
Issues for Non-collocated Deployments with 4Layers per CC |
Qualcomm Incorporated |
| R4-2218831 |
Discussion on inter-band EN-DC with overlapping DL bands (non-co-located) |
MediaTek Inc. |
| R4-2218875 |
Discussion on the new type UE to support non-collocated deployment |
vivo |
| R4-2220534 |
LS to RAN2 on intraBandFreqSeparationUL-AggBW-GapBW-r16 |
Samsung |
| R4-2220537 |
WF on the requirement for intra-band non-collocated CA/EN-DC |
KDDI |
| 8.11.3 |
RRM Core requirements |
|
| R4-2218231 |
Discussion on RRM requirements for non-co-located EN-DC and CA |
MediaTek inc. |
| R4-2218683 |
Draft CR on introducing MRTD/MTTD requirement |
Apple |
| R4-2218687 |
Discussion on RRM requirements for non-collocated FR1 intra-band EN-DC/NR-CA |
Nokia, Nokia Shanghai Bell |
| R4-2218688 |
MRTD/MTTD requirement for intra-band non-collocated CA |
Apple |
| R4-2219255 |
Discussion on RRM impacts due to support intra-band non-collocated CA/DC |
Huawei, HiSilicon |
| R4-2219286 |
Discussion on RRM requirements for intra-band non-collocated EN-DC/NR-CA deployment |
Samsung |
| R4-2219334 |
MRTD and MTTD requirements |
Ericsson |
| R4-2219526 |
Discussion on RRM requirements of Type 2 UE for intra-band non-collocated NR-CA deployment |
KDDI Corporation |
| R4-2220398 |
WF on RRM requirements for intra-band non-collocated EN-DC/NR-CA |
Huawei, HiSilicon, Samsung |
| 8.11.4 |
Moderator summary and conclusions |
|
| R4-2220068 |
Topic summary for [105][222] NonCol_intraB_ENDC_NR_CA_RRM |
Moderator (Huawei) |
| R4-2220113 |
Topic summary for [105][133] NonCol_intraB |
Moderator (KDDI) |
| 8.12.3 |
RF requirement for simultaneous multi-panel operation for train roof-mounted FR2 high power devices |
|
| R4-2218564 |
Deployment scenario and UE assumption for simultaneous multi-panel operation for FR2 HST |
Samsung |
| R4-2219818 |
On Multi-panel RF requirements for NR FR2 HST enhancement |
Huawei, HiSilicon |
| R4-2220536 |
WF on FR2 HST UE RF requirement |
Samsung |
| 8.12.4 |
Study on reference tunnel deployment scenario and UL timing adjustment solution |
|
| R4-2220031 |
Study on reference tunnel scenario and UL timing adjustment |
Qualcomm Incorporated |
| 8.12.4.1 |
Tunnel deployment scenarios |
|
| R4-2219071 |
Tunnel scenairo for enhanced HST FR2 |
Ericsson |
| R4-2219289 |
Discussion on Tunnel deployment sceanrio |
Samsung |
| R4-2219660 |
Discussion on reference tunnel deployment scenario |
Huawei, HiSilicon |
| R4-2219713 |
On Tunnel Deployment Scenarios in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| 8.12.4.2 |
UL timing adjustment solutions |
|
| R4-2218996 |
Discussion on UL timing adjustment solution for FR2 HST |
OPPO |
| R4-2219070 |
UL timing RRM requirements for enhanced HST FR2 |
Ericsson |
| R4-2219254 |
Discussion on UL timing adjustment for R18 FR2 HST |
Huawei, HiSilicon |
| R4-2219714 |
On UL Timing Adjustment in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| 8.12.5.1 |
RRM impact by multi-panel simultaneous reception |
|
| R4-2219073 |
Multi-panel reception requirements for enhanced HST FR2 |
Ericsson |
| R4-2219288 |
Discussion on RRM impact by multi-panel simultaneous reception for FR2 HST UE |
Samsung |
| R4-2219403 |
Discussion on RRM impact by multi-panel simultaneous reception in FR2 eHST |
Huawei, HiSilicon |
| R4-2219715 |
On RRM Impacts by Multi-Panel Simultaneous Reception in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| R4-2219716 |
Simulation Results for Mobility Performance of Multi-Panel UEs in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| R4-2220396 |
WF on NR FR2 HST Tunnel deployment and UL timing adjustment |
Nokia |
| R4-2220397 |
WF on NR FR2 HST RRM Core requirements impact |
Samsung |
| 8.12.5.2 |
RRM impact by CA |
|
| R4-2218575 |
Discussion on RRM requirements for FR2 HST CA |
Xiaomi |
| R4-2219072 |
CA requirements for enhanced HST FR2 |
Ericsson |
| R4-2219404 |
Discussion on RRM impact by CA in FR2 eHST |
Huawei, HiSilicon |
| R4-2219717 |
On RRM Impact by CA in HST FR2 Enhanced |
Nokia, Nokia Shanghai Bell |
| 8.12.6 |
Moderator summary and conclusions |
|
| R4-2220069 |
Topic summary for [105][223] NR_HST_FR2_enh_RRM |
Moderator (Samsung) |
| R4-2220114 |
Topic summary for [105][134] NR_HST_FR2_enh_UERF |
Moderator (Samsung) |
| 8.13 |
Air-to-ground network for NR |
|
| R4-2218030 |
Draft TR 38.876 ATG v0.1.0 |
CMCC |
| 8.13.1 |
FR1 co-existence evaluation for ATG network |
|
| R4-2218642 |
ATG coexistence simulation assumption |
CMCC |
| R4-2218695 |
TP for TR 38.876: frequency error |
Apple |
| R4-2220538 |
TP for TR 38.876: frequency error |
Apple |
| R4-2220826 |
TP for TR 38.876: frequency error |
Apple |
| 8.13.1.1 |
General aspects |
|
| R4-2219611 |
Discussion on coexistence simulation assumption for ATG scenario |
Huawei, HiSilicon |
| R4-2219615 |
TP for TR 38.876 to capture general assumptions |
Huawei, HiSilicon |
| R4-2219634 |
Link bydget analysis of ATG scenarios |
Ericsson |
| R4-2220539 |
TP for TR 38.876 to capture general assumptions |
Huawei, HiSilicon |
| 8.13.1.2 |
Co-existence scenario and network layout |
|
| R4-2218479 |
Discussion on ATG co-existence scenario and network layout |
CATT |
| R4-2218890 |
Discussion on network layout for coexistence evaluation |
LG Electronics UK |
| R4-2219136 |
Coexistence scenarios of Air-to-ground network for NR |
Qualcomm Incorporated |
| R4-2219614 |
TP for TR 38.876 to capture scenarios and network layout |
Huawei, HiSilicon |
| R4-2219635 |
On ATG BS layout |
Ericsson |
| R4-2220540 |
TP for TR 38.876 to capture scenarios and network layout |
Ericsson |
| 8.13.1.3 |
Co-existence system parameters and modeling |
|
| R4-2218480 |
Discussion on ATG co-existence system parameters and modeling |
CATT |
| R4-2219353 |
Further discussion on coexistence evaluation for ATG network |
ZTE Corporation |
| R4-2219616 |
TP for TR 38.876 to capture system parameter assumption and antenna modelling |
Huawei, HiSilicon |
| R4-2219636 |
Co-existence parameters |
Ericsson |
| R4-2220541 |
TP for TR 38.876 to capture system parameter assumption and antenna modelling |
ZTE |
| 8.13.1.4 |
Co-existence simulation results |
|
| R4-2219637 |
Initial simulation results |
Ericsson |
| 8.13.2 |
UE RF requirements |
|
| R4-2218643 |
ATG UE RF requirement |
CMCC |
| R4-2219135 |
Discussions on the ATG UE RF requirements |
Qualcomm Incorporated |
| R4-2220542 |
WF on ATG co-existence evaluation |
CMCC |
| R4-2220543 |
WF on ATG UE RF requirements |
Huawei |
| 8.13.2.1 |
General aspects |
|
| R4-2218693 |
Discussion on ATG general aspects |
Apple |
| 8.13.2.2 |
Tx requirements |
|
| R4-2218694 |
ATG UE Tx RF requirements |
Apple |
| R4-2219354 |
Further discussion on ATG UE Tx RF requirements |
ZTE Corporation |
| R4-2219612 |
Discussion on ATG UE Tx requirements |
Huawei, HiSilicon |
| R4-2219638 |
UE TX RF requirements |
Ericsson |
| 8.13.2.3 |
Rx requirements |
|
| R4-2219355 |
Further discussion on ATG UE Rx RF requirements |
ZTE Corporation |
| R4-2219613 |
Discussion on ATG UE Rx requirements |
Huawei, HiSilicon |
| R4-2219639 |
UE RX RF requirements |
Ericsson |
| 8.13.3 |
BS RF requirements |
|
| R4-2218385 |
Discussion on ATG BS |
Huawei, Hisilicon |
| R4-2218634 |
ATG bands requirements |
CMCC |
| R4-2218832 |
Further Discussions on the ATG BS RF requirements |
Qualcomm CDMA Technologies |
| R4-2218939 |
Draft CR for 38.104: Adding ATG BS class for Base station classes |
CMCC |
| R4-2219356 |
Further discussion on ATG BS RF requirements |
ZTE Corporation |
| R4-2219640 |
BS RF requirements |
Ericsson |
| 8.13.4 |
RRM core requirements |
|
| R4-2218663 |
TP to TR 38.876: RRM requirements for ATG network |
CMCC |
| R4-2220032 |
RRM requirements for NR ATG WI |
Qualcomm Incorporated |
| 8.13.4.1 |
General aspects |
|
| R4-2218430 |
Discussion on general aspects for Rel-18 ATG RRM requirements |
CATT |
| R4-2218664 |
Discussion on general RRM requirements for ATG |
CMCC |
| R4-2218696 |
General aspects for RRM |
Apple |
| R4-2218891 |
Discussion on general issues on ATG RRM |
LG Electronics UK |
| R4-2219237 |
Discussion on general aspects of RRM requirements for ATG |
Huawei, HiSilicon |
| R4-2219429 |
Discussion on general aspects for air-to-ground network for NR |
ZTE Corporation |
| R4-2219825 |
Discussions on general ATG RRM requirements |
Ericsson |
| 8.13.4.2 |
Mobility requirements |
|
| R4-2218431 |
Discussion on mobility requirements for Rel-18 ATG |
CATT |
| R4-2218665 |
Discussion on RRM mobility requirements for ATG |
CMCC |
| R4-2218697 |
Mobility requirements for ATG |
Apple |
| R4-2218893 |
Discussion on RRM mobility requirements for ATG |
LG Electronics UK |
| R4-2219238 |
Discussion on mobility requirements for ATG |
Huawei, HiSilicon |
| R4-2219430 |
Discussion on mobility requirements for air-to-ground network for NR |
ZTE Corporation |
| R4-2219826 |
Discussions on ATG mobility requirements |
Ericsson |
| 8.13.4.3 |
Timing adjustments |
|
| R4-2218432 |
Discussion on timing adjustments for Rel-18 ATG |
CATT |
| R4-2218666 |
Discussion on RRM timing requirements for ATG |
CMCC |
| R4-2218698 |
Timing adjustments |
Apple |
| R4-2218910 |
Discussion on timing for ATG RRM |
LG Electronics UK |
| R4-2219239 |
Discussion on timing requirements for ATG |
Huawei, HiSilicon |
| R4-2219333 |
On timing requirements |
Ericsson |
| R4-2219431 |
Discussion on timing adjustment for air-to-ground network for NR |
ZTE Corporation |
| 8.13.4.4 |
Signaling characteristics |
|
| R4-2218433 |
Discussion on Signaling characteristics for Rel-18 ATG |
CATT |
| R4-2218667 |
Discussion on RRM Signalling characteristics requirements for ATG |
CMCC |
| R4-2219240 |
Discussion on signaling characteristics requirements for ATG |
Huawei, HiSilicon |
| R4-2219432 |
Discussion on signalling characteristics for air-to-ground network for NR |
ZTE Corporation |
| R4-2219827 |
Discussions on signaling characteristics for ATG |
Ericsson |
| 8.13.4.5 |
Measurement requirements |
|
| R4-2218434 |
Discussion on Measurement requirements for Rel-18 ATG |
CATT |
| R4-2218668 |
Discussion on RRM measurement requirements for ATG |
CMCC |
| R4-2218699 |
Measurement aspects |
Apple |
| R4-2218892 |
Discussion on RRM measurement requirement for ATG |
LG Electronics UK |
| R4-2219241 |
Discussion on measurement requirements for ATG |
Huawei, HiSilicon |
| R4-2219319 |
Discussion on measurement requirement in ATG |
Ericsson |
| R4-2219433 |
Discussion on measurement requirements for air-to-ground network for NR |
ZTE Corporation |
| 8.13.4.6 |
Others |
|
| R4-2219828 |
Discussions on other aspects of ATG RRM requirements |
Ericsson |
| 8.13.5 |
Moderator summary and conclusions |
|
| R4-2220070 |
Topic summary for [105][224] NR_ATG_RRM |
Moderator (CMCC) |
| R4-2220115 |
Topic summary for [105][135] NR_ATG_UERF_part1 |
Moderator (CMCC) |
| R4-2220116 |
Topic summary for [105][136] NR_ATG_UERF_part2 |
Moderator (Huawei) |
| R4-2220134 |
Summary for [105][308] NR_ATG_BSRF |
Moderator (ZTE) |
| R4-2220250 |
WF for ATG BS RF requirements |
ZTE |
| 8.14.1 |
General and work plan |
|
| R4-2218845 |
3GPP TR 38.870 v0.1.0 |
vivo |
| R4-2218849 |
LS to RAN5 on UE TxD for OTA testing |
vivo |
| R4-2219687 |
LS on maintain TxD status |
Xiaomi |
| R4-2220267 |
LS to RAN5 on UE TxD for OTA testing |
vivo, Xiaomi |
| 8.14.2.1 |
Anechoic chamber test methodology |
|
| R4-2218075 |
Proposals for TRP tests under one lay UL MIMO |
Huawei Tech.(UK) Co.. Ltd |
| R4-2218359 |
On UL MIMO TRP methodology |
Apple |
| R4-2218561 |
Discussion on test method of NR 2Tx UE |
Samsung |
| R4-2218846 |
Further discussion on Anechoic chamber test methodology |
vivo |
| R4-2218850 |
TP to TR 38.870 on supplement of basic AC test method |
vivo |
| R4-2219134 |
On enhancement of UE TRP and TRS |
Qualcomm Incorporated |
| R4-2219684 |
Further discussion on single-layer UL MIMO test |
Xiaomi |
| R4-2219697 |
On phase difference for 2Tx TRP |
OPPO |
| 8.14.2.2 |
Reverberation chamber test methodology |
|
| R4-2218074 |
On TRP TRS tests using RC |
Huawei Tech.(UK) Co.. Ltd |
| R4-2218727 |
Sampling NR in an Isotropic RC Environment |
Bluetest AB |
| R4-2218809 |
RC Measurements on Absorber Effectiveness for NR |
Bluetest AB |
| R4-2218847 |
Further discussion on Reverberation chamber test methodology |
vivo |
| R4-2219602 |
Reverberation Chamber test method |
OPPO |
| R4-2219685 |
Further discussion on the Reverberation chamber test method |
Xiaomi |
| R4-2219883 |
Discussion on Reverberation Chamber Test Methodology |
CAICT, SAICT |
| 8.14.2.4 |
Testing time reduction |
|
| R4-2218076 |
Possible solutions on testing time reduction methodologies |
Chosun University, RRA |
| R4-2218702 |
Possible solutions on testing time reduction methodologies |
RRA, Chosun University |
| R4-2218724 |
Possible solutions on testing time reduction methodologies |
RRA, Chosun University |
| R4-2218848 |
Antenna patterns for TRP and TRS measurement grid analysis |
vivo |
| R4-2219850 |
Test Time Reduction using Coarser TRP/TRS Measurement Grids for above and below 3 GHz |
Keysight Technologies UK Ltd, vivo |
| 8.14.3 |
Moderator summary and conclusions |
|
| R4-2220156 |
Summary for [105][330] NR_FR1_TRP_TRS_enh |
Moderator (Vivo) |
| R4-2220265 |
WF for test device information collection for the measurement data pool from Rel-17 TRP TRS WI and Rel-17 FR1 MIMO OTA |
Apple |
| R4-2220266 |
WF for Rel-18 TRP TRS WI |
Vivo |
| R4-2220609 |
Ad-hoc minutes for OTA topics |
Vivo |
| R4-2220610 |
WF for Rel-18 TRP TRS WI |
Vivo |
| 8.15.2 |
FR2 MIMO OTA test methodology enhancement |
|
| R4-2218360 |
On MIMO OTA test methodology |
Apple |
| R4-2218562 |
Antenna configuration in FR2 MIMO OTA campaign |
Samsung |
| R4-2218851 |
Further discussion on FR2 MIMO OTA |
vivo |
| R4-2219138 |
On FR2 MIMO OTA requirements |
Qualcomm Incorporated |
| R4-2219340 |
Framework for FR2 MIMO OTA performance requirements development |
CAICT |
| R4-2219384 |
Discussion on FR2 MIMO OTA test methodology enhancement |
Huawei,HiSilicon |
| R4-2219683 |
on the FR2 MIMO OTA |
Xiaomi |
| R4-2220273 |
Framework for FR2 MIMO OTA performance requirements development |
CAICT |
| R4-2220611 |
Framework for FR2 MIMO OTA performance requirements development |
CAICT |
| 8.15.3 |
FR1 MIMO OTA test methodology enhancement |
|
| R4-2218072 |
on introduction of new channel models |
Huawei Tech.(UK) Co.. Ltd |
| R4-2218073 |
on MIMO OTA tests in browsing mode |
Huawei Tech.(UK) Co.. Ltd |
| R4-2218563 |
Necessity and feasibility of hand phantom MIMO OTA test method |
Samsung |
| R4-2218852 |
Further discussion on FR1 MIMO OTA |
vivo |
| R4-2219339 |
Views on FR1 MIMO OTA performance requirements related work |
CAICT |
| R4-2219341 |
On FR1 MIMO OTA test enhancement for smartphone with hand phantom |
CAICT |
| R4-2219682 |
on the FR1 MIMO OTA |
Xiaomi |
| R4-2219849 |
On Phantom Testing and QZ/Test Zone Size |
Keysight Technologies UK Ltd |
| 8.15.4 |
MU assessment |
|
| R4-2218071 |
MU for hand phantom in MIMO OTA tests |
Huawei Tech.(UK) Co.. Ltd |
| 8.15.5 |
Moderator summary and conclusions |
|
| R4-2220157 |
Summary for [105][331] NR_MIMO_OTA_enh |
Moderator (CAICT) |
| R4-2220272 |
WF for Rel-18 MIMO OTA enhancement WI |
CAICT |
| R4-2220612 |
WF for Rel-18 MIMO OTA enhancement W |
CAICT |
| 8.16.1 |
General and work plan |
|
| R4-2219832 |
BS EMC enhancements - Work Plan proposal |
Ericsson |
| R4-2220253 |
BS EMC enhancements - Work Plan proposal |
Ericsson |
| 8.16.2 |
BS EMC enhancements |
|
| R4-2218619 |
Discussion on BS EMC enhancement R18 |
ZTE Corporation |
| R4-2219343 |
Analysis of reference sensitivity level used in immunity test |
Ericsson |
| R4-2220223 |
Discussion on BS EMC enhancement R18 |
ZTE |
| 8.16.3 |
UE EMC enhancements |
|
| R4-2219680 |
further discussion of UE EMC |
Xiaomi |
| 8.16.4 |
Moderator summary and conclusions |
|
| R4-2220135 |
Summary for [105][309] NR_LTE_EMC_enh |
Moderator (Ericsson) |
| R4-2220251 |
WF for BS EMC |
Ericsson |
| R4-2220252 |
WF for UE EMC |
Xiaomi |
| 8.17.1 |
Absolute physical layer throughput requirements with link adaptation |
|
| R4-2218062 |
Discussion on absolute physical layer throughput requirements with link adaptation |
China Telecom |
| R4-2218199 |
Application layer throughput discussion |
Qualcomm Israel Ltd. |
| R4-2218342 |
Discussion on the normative specifications of ATP requirements |
Intel Corporation |
| R4-2218669 |
Discussion on demodulation requirements for ATP |
CMCC |
| R4-2219120 |
Discussion on application layer throughput requirements |
Ericsson |
| R4-2219221 |
Discussion on Physical Layer Data Throughput |
MediaTek inc. |
| R4-2219516 |
Simulation results on Adaptation Absolute Physical Layer requirements |
Huawei, HiSilicon |
| R4-2219517 |
Discussion on Adaptation Absolute Physical Layer performance requirements definition |
Huawei, HiSilicon |
| R4-2219719 |
On Absolute physical layer throughput requirements with link adaptation |
Nokia, Nokia Shanghai Bell |
| R4-2219720 |
ATP Simulation Results |
Nokia, Nokia Shanghai Bell |
| R4-2219786 |
On Requirements for Application Layer Throughput |
Apple |
| 8.17.2 |
Moderator summary and conclusions |
|
| R4-2220153 |
Summary for [105][327] NR_demod_enh3 |
Moderator (China Telecom) |
| R4-2220276 |
WF for ATP requirements |
Intel Corporation |
| 8.18.1 |
General and work plan |
|
| R4-2218483 |
Discussion on reply LS on maximum number of UL subbands for duplex evolution |
CATT |
| R4-2219358 |
Further discussion on reply LS for full duplex BS |
ZTE Corporation |
| R4-2219632 |
On the reply to the RAN1 LS |
Ericsson |
| R4-2219807 |
Discussion on the LSs from RAN1 on interference modelling and number of UL subband |
Nokia, Nokia Shanghai Bell |
| R4-2219885 |
Regarding reply LS on maximum number of UL sub-bands for duplex evolution |
Qualcomm Incoporated |
| R4-2219889 |
Reply LS on maximum number of UL sub-bands for duplex evolution |
Qualcomm |
| 8.18.2 |
Study the feasibility of and impact on RF requirements |
|
| R4-2220248 |
WF for regulatory information collection |
Ericsson |
| 8.18.2.1 |
Adjacent channel co-existence evaluation |
|
| R4-2218482 |
Discussion on the remaining issues for ajacent channel co-existence simulation assumption |
CATT |
| R4-2218644 |
Study on the simulation assumption for adjacent channel co-existence |
CMCC |
| R4-2218725 |
Preliminary results on SBFD adjacent channel coexistence |
Qualcomm CDMA Technologies |
| R4-2218839 |
Additional simulation results related to SBFD adjacent channel co-existence evaluation |
Ericsson |
| R4-2218862 |
Initial simulation results for adjacent channel co-existence evaluation |
vivo |
| R4-2218942 |
Simulation assumptions for SBFD adjacent channel co-existence study |
Samsung |
| R4-2218943 |
Discussion on SBFD co-ex simulation |
Samsung |
| R4-2219145 |
On the co-existence study for NR duplex operation |
Huawei, HiSilicon |
| R4-2219359 |
Further discussion on full duplex coexistence in adjacent channel scenario |
ZTE Corporation |
| R4-2219809 |
Assumptions for SBFD coexistence evaluation |
Nokia, Nokia Shanghai Bell |
| R4-2219894 |
Evaluation of LSin on interference modelling for duplex evolution |
Qualcomm |
| R4-2220247 |
Simulation assumptions for SBFD adjacent channel co-existence study |
Samsung |
| 8.18.2.2.1 |
BS aspect |
|
| R4-2218051 |
SBFD feasibility study and RF impact on BS aspects |
Kumu Networks |
| R4-2218478 |
Further discussion on BS feasibility study for duplex evolution |
CATT |
| R4-2218648 |
study the feasibility of and impact on RF requirements on gNB side |
CMCC |
| R4-2218726 |
BS SBFD feasibility aspects |
Qualcomm CDMA Technologies |
| R4-2218863 |
Further discussion on interference modelling and SBFD operation for full duplex |
vivo |
| R4-2219146 |
Feasibility study from BS RF perspective |
Huawei, HiSilicon |
| R4-2219283 |
Discussion on feasibility and RF impact of SBFD: BS Aspects |
Samsung |
| R4-2219360 |
Further discussion on self-interference and CLI for full duplex from BS perspective |
ZTE Corporation |
| R4-2219633 |
BS RF feasibility considerations |
Ericsson |
| R4-2219810 |
Discussion on SBFD BS RF |
Nokia, Nokia Shanghai Bell, Spark NZ |
| R4-2219872 |
Views on Filtering in BS Rx model for Full Duplex Operation |
Intel Corporation |
| 8.18.2.2.2 |
UE aspect |
|
| R4-2218164 |
Remaining issues on UE-UE CLI modeling |
Apple |
| R4-2218481 |
Discussion of the remaining issues for UE-UE CLI model |
CATT |
| R4-2218645 |
Study the feasibility of and impact on RF requirements on UE aspect |
CMCC |
| R4-2218864 |
Further discussion on interference modelling for full duplex from UE aspect |
vivo |
| R4-2219284 |
Discussion on feasibility and RF impact of SBFD: UE Aspects |
Samsung |
| R4-2219361 |
Further discussion on self-interference and CLI from UE perspective |
ZTE Corporation |
| R4-2219871 |
Views on Filtering in UE Rx model for Full Duplex Operation |
Intel Corporation |
| R4-2219886 |
Modelling UE-UE cross-link interference for SBFD system study |
Qualcomm Incorporated |
| R4-2220034 |
Duplex enhancements co-channel modelling |
MediaTek (Chengdu) Inc. |
| 8.18.3 |
Summary of regulatory aspects |
|
| R4-2218492 |
Sub-Band Full Duplex - Regulatory aspects |
Ericsson |
| R4-2219147 |
TP on regulatory aspects |
Huawei, HiSilicon |
| R4-2219285 |
Discussion on regulatory aspect of NR duplex evolution |
Samsung |
| R4-2219808 |
Regulatory considerations and TP to TR 38.585 on SBDF full duplex operation |
Nokia, Nokia Shanghai Bell |
| 8.18.4 |
Moderator summary and conclusions |
|
| R4-2220136 |
Summary for [105][310] FS_NR_duplex_evo_Part1 |
Moderator (Samsung) |
| R4-2220137 |
Summary for [105][311] FS_NR_duplex_evo_Part2 |
Moderator (CMCC) |
| R4-2220243 |
LS response to RAN1 for interference modelling and Sub-band configuration |
Samsung |
| R4-2220244 |
WF for the feasibility from BS aspect |
Samsung |
| R4-2220245 |
WF for the feasibility from UE aspect |
Qualcomm |
| R4-2220246 |
WF for co-existence study |
CMCC, Samsung |
| R4-2220268 |
Ad-hoc minutes for Duplex Evolution |
Samsung |
| 8.19.2 |
Study of accuracy improvement based on PRS/SRS bandwidth aggregation for intra-band carriers |
|
| R4-2218416 |
Discussion of the impact of group delay on the performance of PRS/SRS aggregation |
LG Electronics Finland |
| R4-2219084 |
Discussion on NR positioning measurement accuracy improvement based on bandwidth aggregation |
Nokia, Nokia Shanghai Bell |
| R4-2219357 |
Further discussion on CA based positioning enhancement |
ZTE Corporation |
| R4-2219411 |
Discussion on RF impairments for NR positioning |
Huawei, HiSilicon |
| R4-2219465 |
RF issues related to bandwidth aggregation for positioning measurement |
Ericsson |
| R4-2220037 |
Study of PRS/SRS bandwidth aggregation - RF aspects |
Qualcomm Incorporated |
| R4-2220438 |
WF on expanded and improved NR positioning |
Ericsson |
| R4-2220544 |
WF for study on expanded and improved NR positioning |
Intel Corporation |
| R4-2220545 |
LS for study on expanded and improved NR positioning |
Qualcomm |
| 8.19.3 |
Study of accuracy improvement based on NR carrier phase measurements |
|
| R4-2219466 |
RF issues related to carrier phase measurement for positioning |
Ericsson |
| R4-2219915 |
Discussion on NR positioning measurement accuracy improvement based on carrier phase measurements |
Nokia, Nokia Shanghai Bell |
| 8.19.4 |
RRM aspects in the study on expanded and improved NR positioning |
|
| R4-2220735 |
Text Proposals to TR 38.859 for Expanded and Improved NR Positioning for RAN4 RRM aspects |
Huawei |
| 8.19.4.1 |
PRS/SRS Bandwidth Aggregation for Intra-band Carriers |
|
| R4-2218441 |
Discussion on RRM aspects on PRS/SRS bandwidth aggregation for intra-band carriers |
CATT |
| R4-2218517 |
Study of PRS/SRS bandwidth aggregation - RRM aspects |
Qualcomm Incorporated |
| R4-2218603 |
RRM aspects in the study on expanded and improved NR positioning |
ZTE Corporation |
| R4-2218611 |
RRM aspects in the study on expanded and improved NR positioning |
ZTE Corporation |
| R4-2218997 |
RRM requirements on PRS SRS Bandwitdh Aggregation |
OPPO |
| R4-2219186 |
RRM aspects in the study on expanded and improved NR positioning |
ZTE Corporation |
| R4-2219467 |
RRM issues related to bandwidth aggregation for positioning measurement |
Ericsson |
| R4-2219552 |
RRM aspects for PRS/SRS CA |
Huawei, HiSilicon |
| R4-2219771 |
RRM aspects for PRS/SRS bandwidth aggregation for intra-band carriers |
Nokia, Nokia Shanghai Bell |
| 8.19.4.2 |
NR Carrier Phase Measurements |
|
| R4-2219468 |
RRM issues related to carrier phase measurement for positioning |
Ericsson |
| R4-2219553 |
RRM aspects for carrier phase measurement |
Huawei, HiSilicon |
| R4-2219772 |
RRM aspects for NR carrier phase measurements |
Nokia, Nokia Shanghai Bell |
| R4-2220439 |
LS on RRM agreements on expanded and improved NR positioning |
Ericsson |
| 8.19.5 |
Moderator summary and conclusions |
|
| R4-2220071 |
Topic summary for [105][225] FS_NR_pos_enh2_RRM |
Moderator (Ericsson) |
| R4-2220117 |
Topic summary for [105][137] FS_NR_pos_UERF |
Moderator (Intel) |
| 8.20.2.1 |
UL Tx switching with single TAG |
|
| R4-2218403 |
UL Tx switching across 3/4 bands with single TAG |
China Telecom |
| R4-2218627 |
UL Tx switching for single TAG |
CMCC |
| R4-2218855 |
Further discussion on UE RF requirements for TxSwitching up to 3 or 4 bands |
vivo |
| R4-2218928 |
Continue discussion on R18 Tx switching – Single TAG |
MediaTek Inc. |
| R4-2219209 |
Further discussion on Tx switching across 3 or 4 bands for single TAG |
ZTE Corporation |
| R4-2219265 |
Discussion on UL Tx switching with single TAG |
Xiaomi |
| R4-2219408 |
Discussion on Multi-carrier enhancements with single TAG |
Huawei, HiSilicon |
| R4-2219590 |
R18 Discussion on Tx switching with single TAG |
OPPO |
| R4-2219876 |
UE behaviour in case non-equal switching time |
Qualcomm Incorporated |
| R4-2220018 |
Views on Tx switching across 3 and 4 bands |
NTT DOCOMO INC. |
| R4-2220546 |
WF on UE Tx switching requirement for single TAG |
China Telecom |
| R4-2220547 |
WF on UE Tx swithing requirement for multiple TAG |
Ericsson |
| R4-2220548 |
LS on Rel-18 Tx switching |
China Telecom |
| 8.20.2.2 |
UL Tx switching with multiple TAGs |
|
| R4-2218404 |
UL Tx switching with two TAGs |
China Telecom |
| R4-2218628 |
UL Tx switching with multiple TAGs |
CMCC |
| R4-2218826 |
Time masks and switching time location for uplink TX switching with dual-TAG |
Ericsson, Sony |
| R4-2218827 |
Introduction of ON/OFF time mask for TX switching across two bands with dual-TAG |
Ericsson |
| R4-2218929 |
Continue discussion on R18 Tx switching for multi-TAG |
MediaTek Inc. |
| R4-2219210 |
Further discussion on Tx switching across 3 or 4 bands for multiple TAG |
ZTE Corporation |
| R4-2219266 |
Discussion on UL Tx switching with multiple TAG |
Xiaomi |
| R4-2219409 |
Discussion on Multi-carrier enhancements with multiple TAG |
Huawei, HiSilicon |
| R4-2219410 |
Draft CR for 38.101-1 to clarify the time mask for switching with multiple TAGs |
Huawei, HiSilicon |
| R4-2219589 |
R18 Discussion on Tx switching with multi TAG |
OPPO |
| R4-2219877 |
UE requirements during overlaps due to NZ-MTTD |
Qualcomm Incorporated |
| 8.20.3 |
RRM core requirements for multi-carrier enhancements |
|
| R4-2218601 |
Discussion on RRM requirements for multi-carrier enhancements |
ZTE Corporation |
| R4-2220417 |
WF on RRM requirements for NR Multi-carrier enhancements |
Huawei |
| 8.20.3.1 |
DL interruption for Tx switching across 3/4 bands |
|
| R4-2218152 |
On DL interruption for Tx switching across 3/4 bands |
Apple |
| R4-2218405 |
DL interruption for Tx switching across 3/4 bands |
China Telecom |
| R4-2218629 |
DL interruption for Tx switching |
CMCC |
| R4-2218781 |
Further discussion on DL interruption for Tx switching across 3 to 4 bands |
vivo |
| R4-2218926 |
DL interruption for Tx switching across 3/4 bands |
Nokia, Nokia Shanghai Bell |
| R4-2219331 |
On timing requirements DL |
Ericsson |
| R4-2219401 |
Discussion on DL interruption for Tx switching across 3/4 bands |
Huawei, HiSilicon |
| 8.20.3.2 |
UL outage time for TX switching with 2 TAGs |
|
| R4-2218153 |
On UL outage time for TX switching with 2 TAGs |
Apple |
| R4-2218406 |
UL outage time for TX switching with 2 TAGs |
China Telecom |
| R4-2218630 |
UL outage time for Tx switching with 2TAGs |
CMCC |
| R4-2218782 |
On UL outage time for TX switching with 2 TAGs |
vivo |
| R4-2218927 |
UL outage time for TX switching with 2 TAGs |
Nokia, Nokia Shanghai Bell |
| R4-2219332 |
On timing requirements DL |
Ericsson |
| R4-2219402 |
UL outage time for TX switching with 2 TAGs |
Huawei, HiSilicon |
| 8.20.4 |
Moderator summary and conclusions |
|
| R4-2220072 |
Topic summary for [105][226] NR_MC_enh_RRM |
Moderator (Huawei) |
| R4-2220118 |
Topic summary for [105][138] NR_MC_enh_UERF |
Moderator (China Telecom) |
| 8.21.2 |
Study of improvement on FR2 SCell/SCG setup/resume |
|
| R4-2218154 |
Study of improvement on FR2 SCell/SCG setup/resume |
Apple |
| R4-2218397 |
Discussion on FR2 SCell/SCG setup/resume |
CMCC |
| R4-2218411 |
Enhancement of FR2 cell measurements in RRC non-connected mode |
Qualcomm Incorporated |
| R4-2218476 |
Discussion of improvement on FR2 SCell/SCG setup/resume |
CATT |
| R4-2218572 |
Discussion on improvement of FR2 Scell and SCG setup |
Xiaomi |
| R4-2218728 |
Discussion on improvement on FR2 SCell/SCG setup/resume |
MediaTek inc. |
| R4-2218796 |
Discussion on the improvement on FR2 SCell/SCG setup/resume |
vivo |
| R4-2218911 |
Discussion on FR2 Scell/SCG setup/resume |
LG Electronics UK |
| R4-2218985 |
On improvement on FR2 Scell SCG setup resume |
OPPO |
| R4-2219396 |
Discussion on improvement on FR2 SCell/SCG setup/resume |
Huawei, HiSilicon |
| R4-2219442 |
Feasible solutions for FR2 SCell/SCG setup/resume delay enhancements |
Nokia, Nokia Shanghai Bell |
| R4-2219649 |
Discussion on study of improvement on FR2 Scell/SCG setup/Resume |
Ericsson |
| 8.21.3 |
L1/L2 based inter-cell mobility |
|
| R4-2218338 |
Discussion on L1/L2 based inter-cell mobility |
Intel Corporation |
| R4-2218475 |
Reply LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility |
CATT |
| R4-2219954 |
Discussion on LS response on L1 intra- and inter- frequency measurement for LTM |
Ericsson |
| R4-2220403 |
WF on NR Mobility Enhancements RRM requirements – Part 1 |
MediaTek |
| R4-2220404 |
Reply LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility |
CATT |
| R4-2220415 |
WF on NR Mobility Enhancements RRM requirements – Part 2 |
Apple, MediaTek |
| R4-2220416 |
LS on improvement in FR2 SCell/SCG setup delay |
MediaTek |
| R4-2220733 |
Reply LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility |
CATT |
| R4-2220734 |
LS on improvement in FR2 SCell/SCG setup delay |
MediaTek |
| 8.21.3.1 |
General aspects and scenarios |
|
| R4-2218070 |
General aspects and scenarios on L1/L2 based inter-cell mobility |
China Telecom |
| R4-2218400 |
Discussion on general aspects for L1/L2 based inter-cell mobility |
CMCC |
| R4-2218412 |
General aspects and scenarios for LLM |
Qualcomm Incorporated |
| R4-2218477 |
Discussion on general aspects and scenarios for L1/L2 based inter-cell mobility |
CATT |
| R4-2218569 |
Discussion on general aspects and scenarios for L1/L2 based inter-cell mobility |
Xiaomi |
| R4-2218600 |
Discussion on L1/L2 based inter-cell mobility |
ZTE Corporation |
| R4-2218729 |
Discussion on general aspects and scenarios of LTM |
MediaTek inc. |
| R4-2218986 |
On general and scenarios of L1/L2 based inter-cell mobility |
OPPO |
| R4-2219179 |
Discussion on general aspects in R18 L1L2-triggered mobility |
vivo |
| R4-2219397 |
General aspects and scenarios on L1/L2 based inter-cell mobility |
Huawei, HiSilicon |
| R4-2219443 |
LTM general aspects and scenarios |
Nokia, Nokia Shanghai Bell |
| R4-2219955 |
On LTM general aspects and scenarios |
Ericsson |
| 8.21.3.2 |
L1-RSRP measurement requirements |
|
| R4-2218155 |
On L1/L2 based inter-cell mobiliy - L1-RSRP measurement requirements |
Apple |
| R4-2218570 |
Discussion on L1-RSRP measurement requirements for L1/L2 based inter-cell mobility |
Xiaomi |
| R4-2218685 |
Reply LS on L1-RSRP measurement |
Apple |
| R4-2218730 |
Discussion on L1-RSRP measurement requirements for LTM |
MediaTek inc. |
| R4-2218731 |
Reply LS on L1 intra&inter- frequency measurement for L1L2-based inter-cell mobility |
MediaTek inc. |
| R4-2218987 |
On L1-RSRP measurement of L1/L2 based inter-cell mobility |
OPPO |
| R4-2219044 |
Discussion on L1-RSRP measurement requirements |
ZTE Corporation |
| R4-2219180 |
Discussion on L1 measurements in R18 L1L2-triggered mobility |
vivo |
| R4-2219398 |
Discussion on L1-RSRP measurement requirements |
Huawei, HiSilicon |
| R4-2219444 |
LTM L1-RSRP Measurement Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2219956 |
On L1 measurement requirements of LTM |
Ericsson |
| R4-2220399 |
Discussion on L1-RSRP measurement requirements |
ZTE Corporation |
| 8.21.3.3 |
L1/L2 inter-cell mobility delay requirements |
|
| R4-2218069 |
Discussion on L1/L2 inter-cell mobility delay requirements |
China Telecom |
| R4-2218156 |
On L1/L2 based inter-cell mobiliy delay requirements |
Apple |
| R4-2218399 |
Discussion on L1/L2 inter-cell mobility delay requirements |
CMCC |
| R4-2218571 |
Discussion on L1/L2 based inter-cell mobility delay |
Xiaomi |
| R4-2218732 |
Discussion on LTM delay requirements |
MediaTek inc. |
| R4-2218988 |
On L1/L2 based inter-cell mobility delay |
OPPO |
| R4-2219045 |
Discussion on L1/L2 inter-cell mobility delay requirements |
ZTE Corporation |
| R4-2219181 |
Discussion on cell switch delay requirements in R18 L1L2-triggered mobility |
vivo |
| R4-2219399 |
Discussion on L1/L2 inter-cell mobility delay requirements |
Huawei, HiSilicon |
| R4-2219445 |
LTM delay requirements |
Nokia, Nokia Shanghai Bell |
| R4-2219957 |
Discussion on L1/L2 based inter-cell mobility |
Ericsson |
| 8.21.3.4 |
Others |
|
| R4-2219182 |
Reply LS to RAN1 on L1 intra- and inter- frequency measurement |
vivo |
| R4-2219400 |
Discussion on LS on L1 intra- and inter- frequency measurement and configurations for L1/L2-based inter-cell mobility |
Huawei, HiSilicon |
| R4-2219446 |
RACH-less LTM |
Nokia, Nokia Shanghai Bell |
| R4-2219958 |
Discussion on timing aspects on L1/L2 based inter-cell mobility |
Ericsson |
| 8.21.5 |
Moderator summary and conclusions |
|
| R4-2220073 |
Topic summary for [105][227] NR_Mob_enh2_part1 |
Moderator (MediaTek) |
| R4-2220074 |
Topic summary for [105][228] NR_Mob_enh2_part2 |
Moderator (Apple) |
| 8.22.2 |
RRM requirements for Rel-17 MUSIM gaps |
|
| R4-2218516 |
On requirements for Rel-17 MUSIM gaps |
Qualcomm Incorporated |
| R4-2220443 |
WF on NR Dual Tx/Rx Multi-SIM |
Vivo |
| R4-2220444 |
LS on priority levels for MUSIM gaps |
Vivo |
| 8.22.2.1 |
General aspects |
|
| R4-2218804 |
On general aspects for RRM requirements for R17 MUSIM gaps |
vivo |
| R4-2219309 |
Discussions on general issues in MUSIM gaps |
Ericsson |
| 8.22.2.2 |
Collisions between gaps and priority rules |
|
| R4-2218157 |
On R18 MUSIM - collisions between gaps and priority rules |
Apple |
| R4-2218402 |
Discussion on collisions between gaps and priority rules for MUSIM gaps |
CMCC |
| R4-2218580 |
Discussion on collisions between gaps and priority rules for Rel-17 MUSIM gaps |
Xiaomi |
| R4-2218684 |
LS on MUSIM gap priority |
Apple |
| R4-2218808 |
On collisions between gaps and priority rules for MUSIM gaps |
vivo |
| R4-2218998 |
Discussion on collision between gap and priority rules |
OPPO |
| R4-2219310 |
Discussions on collision between MUSIM gaps |
Ericsson |
| R4-2219554 |
Discussion on collision handling for MUSIM gaps |
Huawei, HiSilicon |
| R4-2219887 |
Discussion on priority of MUSIM |
Charter Communications, Inc |
| R4-2219890 |
Discussion on Collisions between gaps and priority rules |
Nokia, Nokia Shanghai Bell |
| R4-2219922 |
Discussion on RRM requirements for MUSIM gaps collision handling |
MediaTek inc. |
| 8.22.2.3 |
On network A requirements |
|
| R4-2218158 |
On R18 MUSIM - network A requirements |
Apple |
| R4-2218581 |
Discussion on network A requirements for Rel-17 MUSIM gaps |
Xiaomi |
| R4-2218805 |
On network A requirements for RRM requirements of MUSIM gaps |
vivo |
| R4-2218999 |
Discussion on network A requirements |
OPPO |
| R4-2219311 |
Discussions on NW-A’s requirement in MUSIM gaps |
Ericsson |
| R4-2219555 |
Discussion on NW-A requirements with MUSIM gaps |
Huawei, HiSilicon |
| R4-2219891 |
Discussion on network A requirements |
Nokia, Nokia Shanghai Bell |
| R4-2219923 |
Discussion on NW A RRM requirements for MUSIM |
MediaTek inc. |
| 8.22.2.4 |
On network B requirements |
|
| R4-2218159 |
On R18 MUSIM - network B requirements |
Apple |
| R4-2218582 |
Discussion on network B requirements for Rel-18 MUSIM gaps |
Xiaomi |
| R4-2218806 |
On network B requirements for RRM requirements of MUSIM gaps |
vivo |
| R4-2219000 |
Discussion on network B requirements |
OPPO |
| R4-2219312 |
Discussions on NW-B’s requirement in MUSIM gaps |
Ericsson |
| R4-2219556 |
Discussion on NW-B requirements with MUSIM gaps |
Huawei, HiSilicon |
| R4-2219892 |
Discussion on network B requirements |
Nokia, Nokia Shanghai Bell |
| R4-2219924 |
Discussion on NW B RRM requirements for MUSIM |
MediaTek inc. |
| 8.22.2.5 |
Others |
|
| R4-2218807 |
On overhead and other issues for RRM requirements for R17 MUSIM gaps |
vivo |
| R4-2219001 |
Discussion on other aspects for MUSIM gaps |
OPPO |
| R4-2219313 |
Discussions on other issues in MUSIM gaps |
Ericsson |
| R4-2219557 |
Discussion on other issues related to MUSIM gaps |
Huawei, HiSilicon |
| R4-2219893 |
Discussion on other aspects of MUSIM discussion |
Nokia, Nokia Shanghai Bell |
| 8.22.3 |
Moderator summary and conclusions |
|
| R4-2220075 |
Topic summary for [105][229] NR_DualTxRx_MUSIM |
Moderator (Vivo) |
| 8.23.1.1 |
System parameters |
|
| R4-2218489 |
NTN enhancement: System parameters - Band(s) definition |
Ericsson |
| R4-2219076 |
Ka-band satellite NTN band definition |
Inmarsat, Thales, Hughes/Echostar, Lockheed Martin, ESA |
| R4-2219083 |
Discussion on above 10GHz NTN band |
Nokia, Nokia Shanghai Bell |
| R4-2219378 |
Further discussion on system parameter for NTN in Ka band |
ZTE Corporation |
| R4-2219990 |
NTN UE NS requirements |
Qualcomm Incorporated |
| 8.23.1.2 |
Regulatory information |
|
| R4-2218488 |
NTN enhancement: Regulatory aspects |
Ericsson |
| R4-2219141 |
Regulatory background for satellite NTN Ka band |
Inmarsat, Thales |
| R4-2219604 |
Regulatory information about ESIM |
OPPO |
| R4-2219629 |
Discussion on Rel-18 NTN regulatory information and ka band |
Huawei, HiSilicon |
| R4-2219768 |
About Ka-band proposed for NR-NTN |
HUGHES Network Systems Ltd; Hughes/EchoStar, Thales, Inmarsat |
| 8.23.1.3 |
Others |
|
| R4-2219971 |
Ka band definition and related SAN terminology |
Huawei, HiSilicon |
| 8.23.2 |
Co-existence study for above 10GHz bands |
|
| R4-2218465 |
Discussion on remaining issues about simulation assumptions for above 10GHz NTN co-existence study |
CATT |
| R4-2218490 |
NTN enhancement: coexistence simulations |
Ericsson |
| R4-2219006 |
Simulation assumptions and preliminary co-existence study for above 10GHz NTN co-existence study |
Samsung Electronics Nordic AB |
| R4-2219258 |
Discussion on Ka-band Coexistence Scenario for GEO |
THALES |
| R4-2219379 |
Further discussion on coexistence evaluation for NTN in Ka-band |
ZTE Corporation |
| R4-2219630 |
Discussion on Rel-18 NTN coexistence study assumption |
Huawei, HiSilicon |
| 8.23.3 |
SAN RF requirements |
|
| R4-2218466 |
General consideration on SAN RF requirements for above 10GHz bands |
CATT |
| R4-2218491 |
NTN enhancement: SAN RF requirements |
Ericsson |
| R4-2219380 |
Further discussion on SAN RF requirements for NTN in Ka-band |
ZTE Corporation |
| 8.23.4 |
UE RF requirements |
|
| R4-2219041 |
Discussion for NR to support non-terrestrial networks |
Xiaomi |
| R4-2219336 |
NTN Terminals in above 10 GHz |
THALES |
| R4-2219381 |
Further discussion on UE RF requirements for NTN in Ka-band |
ZTE Corporation |
| R4-2219631 |
Discussion on Ka band NTN UE |
Huawei, HiSilicon |
| R4-2219989 |
NTN UE device types for >10 GHz |
Qualcomm Incorporated |
| R4-2220027 |
RF requirements for NTN UE |
Intel Corporation |
| 8.23.5 |
Moderator summary and conclusions |
|
| R4-2220119 |
Topic summary for [105][139] NR_NTN_enh_UERF |
Moderator (ZTE) |
| R4-2220138 |
Summary for [105][312] NR_NTN_enh_Part1 |
Moderator (Thales) |
| R4-2220139 |
Summary for [105][313] NR_NTN_enh_Part2 |
Moderator (Samsung) |
| R4-2220224 |
Ad-hoc minutes for NTN above 10GHz band introduction |
Qualcomm |
| R4-2220239 |
WF for above 10GHz band definition and system parameters |
Thales |
| R4-2220240 |
WF for above 10GHz SAN RF requirements |
Thales, ZTE |
| R4-2220241 |
WF for NTN coexistence study for above 10GHz |
Samsung |
| R4-2220304 |
WF for above 10GHz SAN RF requirements |
Thales, ZTE |
| R4-2220573 |
WF on NTN UE RF requirements |
ZTE |
| 8.24.1 |
Enhancement of increasing UE power high limit for CA and DC |
|
| R4-2218216 |
Discussion on enhancement of increasing UE power high limit for CA and DC |
Fujitsu Limited |
| R4-2218217 |
DRAFT Reply LS on enhancements to realize increasing UE power high limit for CA and DC |
Fujitsu Limited |
| R4-2218372 |
Coverage enhancements using idled MIMO resources |
Qualcomm Incorporated |
| R4-2218415 |
Scope of increasing UE power high limit for CA and DC |
Nokia, Nokia Shanghai Bell |
| R4-2218828 |
Power-class fallback reporting in the PHR for improved scheduling and enhanced network performance with SAR constraints |
Ericsson |
| R4-2218856 |
Discussion on enhancement of increasing UE power high limit for CA and DC |
vivo |
| R4-2219042 |
Discussion on enhancement of increasing UE maximum power high limit |
Xiaomi |
| R4-2219498 |
On enhancements of increasing UE power high limit for CA and DC |
Huawei, HiSilicon |
| R4-2219595 |
R18 Clarification on inter-band 3Tx requirements |
OPPO |
| R4-2220019 |
View for LS on Enhancement of increasing UE power high limit for CA and DC |
NTT DOCOMO INC. |
| 8.24.2 |
Enhancement to reduce MPR/PAR |
|
| R4-2219499 |
On further enhancements to reduce MPR/PAR |
Huawei, HiSilicon |
| R4-2220550 |
WF on higher power limit increasing for Rel-18 |
Huawei |
| R4-2220551 |
WF on the MPR reduction for coverage enhancement |
Nokia |
| R4-2220552 |
LS on RF simulation parameters to be used in RAN4 for power domain enhancements |
Nokia |
| R4-2220841 |
WF on the MPR reduction for coverage enhancement |
Nokia |
| R4-2220842 |
LS on RF simulation parameters to be used in RAN4 for power domain enhancements |
Nokia |
| 8.24.2.1 |
General and work plan for Enhancement to reduce MPR/PAR |
|
| R4-2218238 |
Scope of the work for MPR/PAR -objective |
Nokia, Nokia Shanghai Bell |
| R4-2219208 |
Discussion on enhancement of increasing UE power high limit for CA and DC |
ZTE Corporation |
| 8.24.2.2 |
RF simulation parameters |
|
| R4-2218237 |
RF simulation parameters for MPR/PAR evaluations |
Nokia, Nokia Shanghai Bell |
| R4-2218877 |
Discussion on RF simulation parameters for enhancement to reduce MPR |
vivo |
| R4-2219797 |
simualtion parameter discussion |
Ericsson |
| 8.24.2.3 |
RF simulation results for transparent schemes |
|
| R4-2218240 |
RF simulation results for transparent schemes |
Nokia, Nokia Shanghai Bell |
| R4-2218373 |
Discussion on some transparent techniques for UL power enhancement |
Qualcomm Incorporated |
| R4-2218878 |
RF simulation results for transparent schemes for enhancement to reduce MPR |
vivo |
| R4-2219795 |
Initial simulation results for the transparent scheme |
Ericsson |
| 8.24.2.4 |
RF simulation results for non-transparent schemes |
|
| R4-2218239 |
RF simulation results for non-transparent schemes |
Nokia, Nokia Shanghai Bell |
| R4-2218879 |
RF simulation results for non-transparent schemes for enhancement to reduce MPR |
vivo |
| R4-2219796 |
Initial simulation results for non-transparent scheme |
Ericsson |
| 8.24.2.5 |
RF specification impact |
|
| R4-2218044 |
Spec. impact of UL power enhancement from transparent techniques |
Qualcomm Incorporated |
| R4-2218248 |
RF specification impacts |
Nokia, Nokia Shanghai Bell |
| R4-2218857 |
RF specification impact for enhancement to reduce MPR |
vivo |
| 8.24.3 |
Moderator summary and conclusions |
|
| R4-2220120 |
Topic summary for [105][140] NR_cov_enh2_part1 |
Moderator (Huawei) |
| R4-2220121 |
Topic summary for [105][141] NR_cov_enh2_part2 |
Moderator (Nokia) |
| 8.25.1 |
General and work plan |
|
| R4-2219374 |
Discussion on RAN4 feature list for NCR-MT |
ZTE Corporation |
| R4-2219805 |
Discussion on NR Network-controlled repeaters |
Nokia, Nokia Shanghai Bell |
| 8.25.2 |
Study of RF core and EMC requirements |
|
| R4-2218487 |
Discussion of NCR RF requirements |
CATT |
| R4-2218639 |
discussion on NCR RF requirements |
CMCC |
| R4-2219375 |
Further discussion on RF requirements for NCR |
ZTE Corporation |
| R4-2219641 |
On NCR RF requirements |
Ericsson |
| R4-2219806 |
Study of RF core requirements of NR Network-controlled repeaters |
Nokia, Nokia Shanghai Bell |
| 8.25.3 |
Study of RRM function and RRM core requirements |
|
| R4-2219256 |
Discussion on RRM impacts for NR network-controlled repeaters |
Huawei, HiSilicon |
| R4-2219376 |
Further discussion on RRM requirements for NCR-MT |
ZTE Corporation |
| R4-2219718 |
On NCR RRM Requirements |
Nokia, Nokia Shanghai Bell |
| R4-2219845 |
Analysis of RRM requirements for network controlled repeater |
Ericsson |
| R4-2220708 |
WF on NR Network-controlled Repeaters RRM requirements |
ZTE |
| 8.25.4 |
Moderator summary and conclusions |
|
| R4-2220076 |
Topic summary for [105][230] NR_netcon_repeater_RRM |
Moderator (ZTE) |
| R4-2220140 |
Summary for [105][314] NR_netcon_repeater |
Moderator (ZTE) |
| R4-2220255 |
WF for NCR system parameters and RF requirements |
ZTE,CMCC |
| 9.1.1 |
Rapporteur input (WID/TR/CR) |
|
| R4-2219905 |
Big CR on Introduction of completed R18 x(x<=6) DL y(y<=2) UL CA band combinations to TS 36.101 |
Huawei Technologies France |
| R4-2219906 |
Revised WID Rel-18 LTE-A CA for x(x<=6) DL y(y<=2) UL |
Huawei Technologies France |
| R4-2219908 |
TR 36.718-02-01 LTE-A CA for x(x=123456) DL y(y=12) UL |
Huawei Technologies France |
| R4-2220601 |
Introduction of completed new LTE-A CA combinations to TS 36.101 |
Huawei Technologies France |
| 9.1.4 |
Moderator summary and conclusions |
|
| R4-2220090 |
Topic summary for [105][110] LTE_Baskets |
Moderator (Huawei) |
| 9.2.1 |
General and work plan |
|
| R4-2218649 |
CR for 36.101: UE RF requirements for band 8 intra-band contiguous CA |
CMCC |
| 9.3.1 |
General |
|
| R4-2218035 |
Revised WID proposal for Introduction of LTE TDD band in 1670-1675 MHz |
Ligado Networks |
| R4-2218497 |
CR to TS 36.133: Introduction of LTE TDD band 54 |
Ericsson |
| 9.3.2 |
UE RF requirements |
|
| R4-2218031 |
CR related to Introduction of new LTE TDD Band in 1670 – 1675 MHz |
Ligado Networks, Skyworks Solutions, Inc., Nokia |
| R4-2218032 |
CR related to Introduction of new LTE TDD Band in 1670 – 1675 MHz |
Ligado Networks, Skyworks Solutions, Inc., Nokia |
| R4-2218033 |
CR related to Introduction of new LTE TDD Band in 1670 – 1675 MHz |
Ligado Networks, Skyworks Solutions, Inc., Nokia |
| R4-2218034 |
CR related to Introduction of new LTE TDD Band in 1670 – 1675 MHz |
Ligado Networks, Skyworks Solutions, Inc., Nokia |
| R4-2220497 |
CR related to Introduction of new LTE TDD Band in 1670 – 1675 MHz |
Ligado Networks, Skyworks Solutions, Inc., Nokia |
| R4-2220498 |
CR related to Introduction of new LTE TDD Band in 1670 – 1675 MHz |
Ligado Networks, Skyworks Solutions, Inc., Nokia |
| R4-2220499 |
CR related to Introduction of new LTE TDD Band in 1670 – 1675 MHz |
Ligado Networks, Skyworks Solutions, Inc., Nokia |
| R4-2220500 |
CR related to Introduction of new LTE TDD Band in 1670 – 1675 MHz |
Ligado Networks, Skyworks Solutions, Inc., Nokia |
| 9.3.3 |
BS RF requirements |
|
| R4-2218494 |
CR to TS 37.105: Introduction of LTE TDD band 54 |
Ericsson |
| R4-2218495 |
CR to TS 37.145-1: Introduction of LTE TDD band 54 |
Ericsson |
| R4-2218496 |
CR to TS 37.145-2: Introduction of LTE TDD band 54 |
Ericsson |
| R4-2219853 |
CR to 38.141-1 on introduction of Band 54 |
Nokia, Nokia Shanghai Bell |
| R4-2219854 |
CR to 38.141-2 on introduction of Band 54 |
Nokia, Nokia Shanghai Bell |
| R4-2219855 |
CR to 36.104 on introduction of Band 54 |
Nokia, Nokia Shanghai Bell |
| R4-2219856 |
CR to 36.141 on introduction of Band 54 |
Nokia, Nokia Shanghai Bell |
| R4-2219857 |
CR to 37.104 on introduction of Band 54 |
Nokia, Nokia Shanghai Bell |
| R4-2219858 |
CR to 37.141 on introduction of Band 54 |
Nokia, Nokia Shanghai Bell |
| R4-2219859 |
CR to 38.104 on introduction of Band 54 |
Nokia, Nokia Shanghai Bell |
| 9.3.4 |
Moderator summary and conclusions |
|
| R4-2220101 |
Topic summary for [105][121] R18_LTE_TDD_1.6GHz |
Moderator (Ligado) |
| 9.4.2 |
Band definition and system parameters |
|
| R4-2218493 |
5G Broadcast: Bands discussion |
Ericsson |
| R4-2219190 |
Discussion on band definition for LTE based broadcast |
ZTE Corporation |
| R4-2219627 |
Discussion on UE implementation for band plan |
Huawei, HiSilicon |
| R4-2219708 |
LTE based 5G broadcast band definition |
Nokia, Nokia Shanghai Bell |
| R4-2219987 |
UHF band plan for 5G broadcast |
Qualcomm Incorporated |
| 9.4.3 |
UE RF requirement maintenance |
|
| R4-2219191 |
Discussion on UE RF requirement maintenance |
ZTE Corporation |
| R4-2219628 |
Discussion on UE RF requirements |
Huawei, HiSilicon |
| R4-2219709 |
LTE based 5G UE RF open issues |
Nokia, Nokia Shanghai Bell |
| R4-2219988 |
UE ACS requirement for 5G broadcast |
Qualcomm Incorporated |
| R4-2220501 |
WF on UE RF for 5G broadcast |
Qualcomm Technologies Int |
| 9.4.4 |
BS RF requirement maintenance |
|
| R4-2218067 |
BS requirements for 5G terrestrial broadcast |
SWR |
| R4-2219372 |
Further discussion on BS RF requirements for LTE based broadcast |
ZTE Corporation |
| R4-2219864 |
BS requirements for LTE based 5G terrestrial broadcast band(s) |
Nokia, Nokia Shanghai Bell |
| R4-2219972 |
Initial analysis of the regulatory document (GB20600-2006) |
Huawei, HiSilicon |
| 9.4.5 |
Moderator summary and conclusions |
|
| R4-2220102 |
Topic summary for [105][122] LTE_terr_bcast_bands_UERF |
Moderator (Qualcomm) |
| R4-2220141 |
Summary for [105][315] LTE_terr_bcast_bands_BSRF |
Moderator (Nokia) |
| R4-2220254 |
WF for BS requirements for 5G terrestrial broadcast |
Nokia |
| 9.5.1 |
General and work plan |
|
| R4-2218241 |
Work Plan for NB-IoT/eMTC for NTN requirements |
MediaTek inc. |
| R4-2219791 |
On IoT NTN UE RF requirement due to doppler pre-compensation |
Ericsson |
| R4-2219973 |
Work-plan for the TS 36.181 specification for SAN RF conformance testing |
Huawei, HiSilicon |
| R4-2219974 |
draft CR to TS 36.307: release independence requirements introduction for NTN IoT, Rel-17 |
Huawei, HiSilicon |
| R4-2219975 |
draft CR to TS 36.307: release independence requirements introduction for NTN IoT, Rel-18 |
Huawei, HiSilicon |
| R4-2220811 |
draft CR to TS 36.307: release independence requirements introduction for NTN IoT, Rel-17 |
Huawei, HiSilicon |
| 9.5.2 |
System parameters |
|
| R4-2219271 |
TP on channel number offset for NB-IoT NTN |
Huawei, HiSilicon |
| R4-2219363 |
Further discussion on system parameters |
ZTE Corporation |
| R4-2219790 |
On System parameter for IoT NTN |
Ericsson |
| R4-2220025 |
System parameters remaining issues |
MediaTek (Chengdu) Inc. |
| R4-2220812 |
TP on channel number offset for NB-IoT NTN |
Huawei, HiSilicon |
| 9.5.3 |
Co-existence verification |
|
| R4-2219133 |
Coexistence simulation restuls for TN-NTN NB IoT |
Qualcomm Incorporated |
| R4-2219364 |
Further discussion on simulation assumptions and evaluation results for IoT over NTN |
ZTE Corporation |
| R4-2219787 |
IoT NTN coexisting results |
Ericsson |
| R4-2220022 |
Adjacent channel coexistence remaining issues |
MediaTek (Chengdu) Inc. |
| 9.5.4 |
SAN RF requirements |
|
| R4-2219362 |
Draft spec for TS 36.108 |
ZTE Corporation |
| R4-2219365 |
Further discussion on SAN RF requirements for IoT over NTN |
ZTE Corporation |
| R4-2219366 |
TP for TS 36.108: Section 1,2,3 |
ZTE Corporation |
| R4-2219367 |
TP for TS 36.108: Clause 7 |
ZTE Corporation |
| R4-2219368 |
TP for TS 36.108: Clause 10 |
ZTE Corporation |
| R4-2219369 |
TP for TS 36.108: Annex |
ZTE Corporation |
| R4-2219792 |
TP for SAN RF requirement clause 9 |
Ericsson |
| R4-2219793 |
TP for SAN RF requirement clause 6 |
Ericsson |
| R4-2219794 |
IoT SAN RF remaining issues |
Ericsson |
| R4-2219976 |
Discussion on the implementation aspects of the release independence requirements introduction for NTN IoT |
Huawei, HiSilicon |
| R4-2219977 |
TP to TS 36.108: removal of colocation requirements |
Huawei, HiSilicon |
| R4-2219978 |
TP to TS 36.108 (section 4) |
Huawei, HiSilicon |
| R4-2219979 |
TP to TS 36.108 (section 5) |
Huawei, HiSilicon |
| R4-2219980 |
Initial discussion on the conformance testing specification TS 36.181 for the IoT NTN SAN RF |
Huawei, HiSilicon |
| R4-2220296 |
TP for TS 36.108: Section 1,2,3 |
ZTE Corporation |
| R4-2220297 |
TP for TS 36.108: Clause 7 |
ZTE Corporation |
| R4-2220298 |
TP for TS 36.108: Clause 10 |
ZTE Corporation |
| R4-2220299 |
TP for TS 36.108: Annex |
ZTE Corporation |
| R4-2220300 |
TP for SAN RF requirement clause 9 |
Ericsson |
| R4-2220301 |
TP for SAN RF requirement clause 6 |
Ericsson |
| R4-2220302 |
TP to TS 36.108 (section 4) |
Huawei, HiSilicon |
| R4-2220303 |
TP to TS 36.108 (section 5) |
Huawei, HiSilicon |
| R4-2220614 |
TP to TS 36.108 (section 5) |
Huawei, HiSilicon |
| 9.5.5 |
UE RF requirements |
|
| R4-2218036 |
FCC Part §25.202(f) discussion and implications on SEM, spurious emissions requirements and A-MPR for IoT NTN UE |
Ligado Networks |
| R4-2218376 |
TS 36.102 v0.2.0 |
Mediatek India Technology Pvt. |
| R4-2218377 |
TS 36.102 v0.3.0 |
Mediatek India Technology Pvt. |
| R4-2218421 |
Discussion on UE RF requirements for IoT NTN |
Mediatek India Technology Pvt. |
| R4-2218767 |
TP for IoT NTN RF requirement on ACS |
Sony |
| R4-2219039 |
Discussion on UE spurious emission requirement for NB-iot/eMTC NTN |
Xiaomi |
| R4-2219040 |
TP for TS 36.102 on spurious emission for NB-iot eMTC NTN |
Xiaomi |
| R4-2219270 |
Discussion on UE frequency error requirement for IoT NTN |
Huawei, HiSilicon |
| R4-2219370 |
Further discussion on UE RF requirements for IoT over NTN |
ZTE Corporation |
| R4-2219371 |
TP for TS 36.102: Clause 6.5.3 |
ZTE Corporation |
| R4-2219475 |
TP to TS 36.102 on MPR and A-MPR and discussion on emission requirements |
Qualcomm Inc. |
| R4-2219788 |
IoT UE RF remaining issues |
Ericsson |
| R4-2219789 |
TP for UE RF requirement - Frequency error |
Ericsson |
| R4-2219867 |
TP on UE ACLR and SEM for IoT NTN |
Huawei, HiSilicon |
| R4-2219878 |
UE behaviour with mandatory frequency pre-compensation |
Qualcomm Incorporated |
| R4-2220023 |
TP on TS36.102 Clause 2, 3 and 4 |
MediaTek (Chengdu) Inc. |
| R4-2220028 |
TP on suffix clause levels and other clarifications |
MediaTek (Chengdu) Inc. |
| R4-2220046 |
TP for 36.102 for NB frequency error |
Qualcomm Incorporated |
| R4-2220802 |
TP for TS 36.102: Clause 6.5.3 |
ZTE Corporation |
| R4-2220803 |
TP to TS 36.102 on MPR and A-MPR and discussion on emission requirements |
Qualcomm Inc. |
| R4-2220804 |
TP for UE RF requirement - Frequency error |
Ericsson |
| R4-2220805 |
TP on suffix clause levels and other clarifications |
MediaTek (Chengdu) Inc. |
| R4-2220806 |
TP for 36.102 for NB frequency error |
Qualcomm Incorporated |
| R4-2220828 |
TP on TS36.102 Clause 2, 3 and 4 |
MediaTek (Chengdu) Inc. |
| R4-2220835 |
TP for TS 36.102: Clause 6.5.3 |
ZTE Corporation |
| R4-2220836 |
TP on UE ACLR and SEM for IoT NTN |
Huawei, HiSilicon |
| 9.5.6 |
RRM core requirements |
|
| R4-2218232 |
RRM requirements for LTE NB-IoT/eMTC over NTN |
MediaTek inc. |
| R4-2218233 |
Big draftCR for IoT NTN core requirements for TS36.133 for draftCRs endorsed in RAN4#104-bis-e |
MediaTek inc. |
| R4-2218234 |
Introduction of cell re-selection and PUR requirement for UE category NB-IoT for Satellite Access |
MediaTek inc. |
| R4-2218235 |
Introduction of RRC Re-establishment requirement for NB-IoT UEs for Satellite Access |
MediaTek inc. |
| R4-2218413 |
RRM requirements of IoT NTN |
Qualcomm Incorporated |
| R4-2218670 |
Discussion on RRM core requirements for LTE NB-IoT and eMTC NTN |
CMCC |
| R4-2218671 |
draft CR on RRC re-establishment and timing requirement for eMTC UE in IoT-NTN |
CMCC |
| R4-2219074 |
Draft CR on RLM for category M1 UE |
Ericsson |
| R4-2219230 |
Discussion RRM requirements for IoT NTN |
Huawei, HiSilicon |
| R4-2219231 |
DraftCR on RLM requirements for NB-IoT for IoT NTN |
Huawei, HiSilicon |
| R4-2219489 |
Discussion on RRM Core Requirements for IoT over NTN |
Nokia, Nokia Shanghai Bell |
| R4-2219558 |
draftCR on HO requirements for eMTC over NTN |
Huawei, HiSilicon |
| R4-2219559 |
draftCR on measurement requirements for eMTC over NTN |
Huawei, HiSilicon |
| R4-2219822 |
Discussions on NTN IoT RRM requirements |
Ericsson |
| R4-2219823 |
IDLE mode requirements for IoT NTN (cat-M) |
Ericsson |
| R4-2219844 |
Draft CR on RRC release with redirection for Cat-M1 for satellite access in 36.133 |
Ericsson |
| R4-2220363 |
Introduction of cell re-selection and PUR requirement for UE category NB-IoT for Satellite Access |
MediaTek inc. |
| R4-2220364 |
Introduction of RRC Re-establishment requirement for NB-IoT UEs for Satellite Access |
MediaTek inc. |
| R4-2220365 |
draft CR on RRC re-establishment and timing requirement for eMTC UE in IoT-NTN |
CMCC |
| R4-2220366 |
Draft CR on RLM for category M1 UE |
Ericsson |
| R4-2220367 |
DraftCR on RLM requirements for NB-IoT for IoT NTN |
Huawei, HiSilicon |
| R4-2220368 |
draftCR on HO requirements for eMTC over NTN |
Huawei, HiSilicon |
| R4-2220369 |
IDLE mode requirements for IoT NTN (cat-M) |
Ericsson |
| R4-2220412 |
Big CR for IoT NTN core requirements for TS36.133 |
MediaTek |
| 9.5.7 |
RRM performance requirements |
|
| R4-2219232 |
Discussion performance requirements for IoT NTN |
Huawei, HiSilicon |
| R4-2219824 |
Discussions on IoT NTN performance requirements |
Ericsson |
| R4-2220362 |
WF on NTN NB-IoT/eMTC RRM requirements |
MediaTek |
| 9.5.8 |
UE Demodulation requirements |
|
| R4-2218242 |
General views on IoT-NTN UE demodulation requirements |
MediaTek inc. |
| R4-2218974 |
NTN NB-IoT/eMTC demodulation performance requirements |
Qualcomm India Pvt Ltd |
| R4-2219119 |
Discussion on eMTC/NB-IoT UE demodulation requirements for NTN |
Ericsson |
| R4-2219661 |
Discussion on LTE NTN IOT demod |
Huawei, HiSilicon |
| 9.5.9 |
Moderator summary and conclusions |
|
| R4-2220077 |
Topic summary for [105][231] LTE_NBeMTC_NTN_RRM |
Moderator (MediaTek) |
| R4-2220122 |
Topic summary for [105][142] LTE_NBeMTC_NTN_UERF |
Moderator (MediaTek) |
| R4-2220142 |
Summary for [105][316] IoT_NTN_Co-existence_SANRF |
Moderator (ZTE) |
| R4-2220154 |
Summary for [105][328] IoT_NTN_Demod |
Moderator (MTK) |
| R4-2220242 |
WF for IoT over NTN SAN RF requirements |
Ericsson |
| R4-2220278 |
WF for IoT over NTN UE demodulation requirements |
MediaTek |
| R4-2220574 |
WF on UE RF requirements for LTE_NBeMTC_NTN_UERF |
MediaTek |
| R4-2220575 |
Ad hoc minutes for UE RF requirements for LTE_NBeMTC_NTN_UERF |
MediaTek |
| 10.1.1 |
Maximum uplink timing difference for multi-DCI multi-TRP with two TAs (R1-2205593) |
|
| R4-2218160 |
On R18 eFeMIMO - MTTD for multi-DCI mult-TRP with two TAs |
Apple |
| R4-2218585 |
on Maximum uplink timing difference for multi-DCI multi-TRP with two TAs |
Xiaomi |
| R4-2218938 |
Maximum Uplink Time Difference for Multi-DCI Multi-TRP with 2 TAs |
Nokia, Nokia Shanghai Bell |
| R4-2219033 |
Discussion on maximum uplink timing difference for Multi-DCI multi-TRP with two Tas |
Samsung |
| R4-2219183 |
Discussion on maximum uplink timing difference for multi-DCI multi-TRP with two TAs |
vivo |
| R4-2219257 |
On maximum uplink timing difference for multi-DCI multi-TRP with two TAs |
Huawei, HiSilicon |
| R4-2219959 |
Discussion on MTTD for multi-DCI multi-TRP with two TAs |
Ericsson |
| 10.1.2 |
UE power limitation for STxMP in FR2 (R1-2205639) |
|
| R4-2218039 |
Reply LS on UE power limitation for STxMP in FR2 (R1-2205639) |
Qualcomm Incorporated |
| R4-2218131 |
UE power limits and panel definition for STxMP mDCI case |
InterDigital Communications |
| R4-2218861 |
Further discussion and reply LS on UE power limitation for STxMP in FR2 |
vivo |
| R4-2218885 |
Reply LS on UE power limitation for STxMP in FR2 |
Samsung |
| R4-2219500 |
draft Reply LS reply on the UE power limitation for STxMP in FR2 |
Huawei, HiSilicon |
| R4-2220579 |
Reply LS on UE power limitation for STxMP in FR2 |
Samsung |
| 10.1.3 |
Others |
|
| R4-2218045 |
Reply LS on enhancements to realize increasing UE power high limit for CA and DC (R1-2210739) |
Qualcomm Incorporated |
| R4-2220584 |
Reply LS on enhancements to realize increasing UE power high limit for CA and DC (R1-2210739) |
Qualcomm Incorporated |
| 10.2.1.1 |
DL-PRS measurements with reduced samples capability (R1-2207940, R2-2208797) |
|
| R4-2218511 |
On the UE capabilities for DL-PRS measurements with reduced number of samples |
Qualcomm Incorporated |
| R4-2218786 |
Draft Reply LS on DL-PRS measurements with reduced samples capability |
vivo |
| R4-2219002 |
Discussion on DL-PRS measurement with reduced capability |
OPPO |
| R4-2219460 |
Reply LS to DL-PRS measurements with reduced samples capability |
Ericsson |
| R4-2219773 |
DL-PRS measurements with reduced samples capability (R1-2207940, R2-2208797) |
Nokia, Nokia Shanghai Bell |
| R4-2220394 |
WF on update of UE feature list for DL-PRS measurements with reduced samples capability |
Ericsson |
| R4-2220728 |
WF on update of UE feature list for DL-PRS measurements with reduced samples capability |
Ericsson |
| 10.2.1.2 |
Capability for PRS measurement without MG (R2-2209241) |
|
| R4-2218449 |
Reply LS on capability for PRS measurement without MG |
CATT |
| R4-2218512 |
On the RAN4 capability for PRS measurements without MG |
Qualcomm Incorporated |
| R4-2218787 |
Draft Reply LS on UE capability for PRS measurement without MG |
vivo |
| R4-2219003 |
Discussion on on capability for PRS outside MG |
OPPO |
| R4-2219459 |
Reply LS to capability for PRS measurement without MG |
Ericsson |
| R4-2219560 |
Reply LS on capability for PRS measurement without MG |
Huawei, HiSilicon |
| R4-2219774 |
Capability for PRS measurement without MG (R2-2209241) |
Nokia, Nokia Shanghai Bell |
| R4-2220392 |
Reply LS on capability for PRS measurement without MG |
CATT |
| 10.2.1.3 |
Support of positioning in FR2-2 (R2-2208810) |
|
| R4-2218450 |
Reply LS on support of positioning in FR2-2 |
CATT |
| R4-2218513 |
On support of NR positioning in FR2-2 |
Qualcomm Incorporated |
| R4-2218788 |
Draft Reply LS on support of positioning in FR2-2 |
vivo |
| R4-2219004 |
Discussion on positioning in FR2-2 |
OPPO |
| R4-2219463 |
Reply LS to support of positioning in FR2-2 |
Ericsson |
| R4-2219561 |
Reply LS on support of positioning in FR2-2 |
Huawei, HiSilicon |
| R4-2219775 |
Support of positioning in FR2-2 (R2-2208810) |
Nokia, Nokia Shanghai Bell |
| R4-2219925 |
Discussion on support of positioning in FR2-2 |
MediaTek inc. |
| R4-2220391 |
Reply LS on support of positioning in FR2-2 |
Huawei, HiSilicon |
| 10.2.1.4 |
Applicability of timing error margin of Rx TEG (R2-2210977) |
|
| R4-2218451 |
Reply LS on applicability of timing error margin of Rx TEG |
CATT |
| R4-2218452 |
CR on applicability of timing error margins in R17 positioning accuracy requirements |
CATT |
| R4-2218514 |
On the applicability of timing error margins for TEGs |
Qualcomm Incorporated |
| R4-2218785 |
Draft Reply LS on applicability of timing error margin of Rx TEG |
vivo |
| R4-2219005 |
Discussion on applicability of timing error margin |
OPPO |
| R4-2219464 |
Response to reply LS on applicability of timing error margin of Rx TEG |
Ericsson |
| R4-2219562 |
Reply LS on applicability of timing error margin of Rx TEG |
Huawei, HiSilicon |
| R4-2219916 |
Applicability of timing error margin of Rx TEG (R2-2210977) |
Nokia, Nokia Shanghai Bell |
| R4-2219926 |
Discussion on the applicability of timing error margin of Rx TEG |
MediaTek inc. |
| R4-2220393 |
Response to reply LS on applicability of timing error margin of Rx TEG |
Ericsson |
| R4-2220729 |
Response to reply LS on applicability of timing error margin of Rx TEG |
Ericsson |
| 10.2.2 |
RLM/BFD relaxation for ePowSav (R2-2209130) |
|
| R4-2218236 |
Discussion on RLM/BFD relaxation and deactivated PSCell requirement |
MediaTek inc. |
| R4-2218420 |
CR on RLM/BFD relaxation and deactivated PSCell requirement |
MediaTek inc. |
| R4-2218583 |
Discussion on remaining issues on RLM/BFD relaxation for ePowSav |
Xiaomi |
| R4-2218989 |
Discussion on LS on RLM/BFD relaxation for ePowSav |
OPPO |
| R4-2219048 |
RLM/BFD relaxation for ePowSav for deactivated SCG |
Nokia, Nokia Shanghai Bell |
| R4-2219049 |
CR for RLM/BFD relaxation for ePowSav for deactivated SCG |
Nokia, Nokia Shanghai Bell |
| R4-2219184 |
Discussion and draft reply LS on remaining issues in R17 RLM BFD relaxation for UE power saving |
vivo |
| R4-2219185 |
CR on R17 relaxed RLM and BFD requirements for deactivated SCG |
vivo |
| R4-2220395 |
WF on RLM/BFD relaxation for ePowSav |
Vivo |
| R4-2220731 |
Reply LS on RLM/BFD relaxation for ePowSav |
Vivo |
| 10.2.3 |
On the ue-PowerClassPerBandPerBC-r17(R4 16-8) (R2-2211023) |
|
| R4-2218295 |
Clarification of ue-PowerClassPerBandPerBC-r17 |
Nokia, Nokia Shanghai Bell |
| R4-2218604 |
Draft Reply LS on applicability of timing error margin |
ZTE Corporation |
| R4-2218605 |
LS to RAN2 on capability for PRS measurement without MG |
ZTE Corporation |
| R4-2218612 |
Draft Reply LS on applicability of timing error margin |
ZTE Corporation |
| R4-2218613 |
LS to RAN2 on capability for PRS measurement without MG |
ZTE Corporation |
| R4-2218759 |
Reply LS on clarification for ue-PowerClassPerBandPerBC-r17 |
Samsung |
| R4-2218853 |
Discussion and reply LS on ue-PowerClassPerBandPerBC-r17 |
vivo |
| R4-2219187 |
Draft Reply LS on applicability of timing error margin |
ZTE Corporation |
| R4-2219188 |
LS to RAN2 on capability for PRS measurement without MG |
ZTE Corporation |
| R4-2219211 |
Discussion and draft reply LS on ue-PowerClassPerBandPerBC-r17 |
ZTE Corporation |
| R4-2219588 |
R17 Reply LS on per band per BC power class |
OPPO |
| R4-2220021 |
Draft reply LS on ue-PowerClassPerBandPerBC-r17 |
MediaTek |
| R4-2220580 |
Reply LS on clarification for ue-PowerClassPerBandPerBC-r17 |
Samsung |
| R4-2220813 |
Reply LS on clarification for ue-PowerClassPerBandPerBC-r17 |
Samsung |
| 10.2.4.1 |
DC location for FR1 enhancement (R2-2209002) |
|
| R4-2218876 |
Discussion and reply LS on DC location reporting |
vivo |
| R4-2219585 |
R17 Discussion on mapping of DC location reporting schemes and LS reply |
OPPO |
| R4-2219586 |
R17 CR on introduction of FR1 CA DC location reporting |
OPPO |
| R4-2219587 |
R17 CR on introduction of FR2 CA DC location reporting |
OPPO |
| R4-2219879 |
Rel-17 DC location method and impact to ran4 specs |
Qualcomm Incorporated |
| R4-2219880 |
draftCR on FR1 Rel-17 DC location |
Qualcomm Incorporated |
| R4-2219881 |
draftCR on FR2 Rel-17 DC location |
Qualcomm Incorporated |
| R4-2220581 |
LS on DC location reporting |
Vivo, OPPO |
| R4-2220582 |
draftCR on FR1 Rel-17 DC location |
Qualcomm Incorporated |
| R4-2220583 |
R17 CR on introduction of FR2 CA DC location reporting |
OPPO, Qualcomm, Huawei |
| R4-2220814 |
LS on DC location reporting |
Vivo, OPPO |
| R4-2220833 |
CR for 38.101-1 for DC location R17 method |
Qualcomm |
| R4-2220834 |
R17 CR on introduction of FR2 CA DC location reporting |
OPPO, Qualcomm, Huawei |
| R4-2220839 |
R17 CR on introduction of FR2 CA DC location reporting |
OPPO, Qualcomm, Huawei |
| 10.2.4.2 |
LS on FR2 UL gap (R2-2211043) |
|
| R4-2218171 |
Draft reply LS on FR2 UL gap |
Apple |
| R4-2218172 |
CR on removing the redundancy from TS 38.133 in response to RAN2 LS |
Apple |
| R4-2220730 |
Reply LS on FR2 UL gap |
Apple |
| 10.2.5 |
Clarification of RACH prioritization rules between LTE and NR-U (R1-2207935, R2-2211015) |
|
| R4-2219927 |
Formal CR to 38.133 Corrections on Handover with PSCell from NR SA to EN-DC with PSCell using CCA |
MediaTek inc. |
| R4-2220385 |
Formal CR to 38.133 Corrections on Handover with PSCell from NR SA to EN-DC with PSCell using CCA |
MediaTek inc. |
| 10.2.6 |
Others |
|
| R4-2219267 |
Reply LS on NS_50 A-MPR |
Huawei, HiSilicon |
| R4-2220585 |
Reply LS on NS_50 A-MPR |
Huawei, HiSilicon |
| 10.3.1 |
Lower humidity limit in normal temperature test environment (R5-221604) |
|
| R4-2218886 |
Reply LS on humidity inconsistency among specifications |
Samsung |
| R4-2218887 |
CR to TS 38.101-1 on humidity condition for normal temperature |
Samsung |
| R4-2218888 |
CR to TS 38.101-2 on humidity condition for normal temperature |
Samsung |
| R4-2219761 |
Discussion on how to resolve the inconsistency of relative humidity limit |
ZTE Corporation |
| R4-2219819 |
On humidity limit inconsistency |
Huawei, HiSilicon |
| R4-2220586 |
Reply LS on humidity inconsistency among specifications |
Samsung |
| 10.3.2 |
ModifiedMPR-Behaviour clarification for different power classes |
|
| R4-2218278 |
Reply LS to RAN5 LS on ModifiedMPR-Behaviour clarification for different power classes |
Nokia |
| R4-2218279 |
CR R17 ModifiedMPR |
Nokia |
| R4-2218280 |
CR R16 ModifiedMPR |
Nokia |
| R4-2219126 |
Discussion the reply LS on Modified MPR-Behaviour clarification for different power classes |
Xiaomi |
| R4-2219570 |
On ModifiedMPR |
Huawei, HiSilicon |
| R4-2219571 |
draft Reply LS on ModifiedMPR |
Huawei, HiSilicon |
| R4-2220593 |
CR R17 ModifiedMPR |
Nokia |
| R4-2220815 |
draft Reply LS on ModifiedMPR-Behaviour clarification for different power classes |
Huawei, HiSilicon |
| 10.4 |
Moderator summary and conclusions |
|
| R4-2220079 |
Topic summary for [105][233] Reply_LS_1 |
Moderator (Apple) |
| R4-2220080 |
Topic summary for [105][234] Reply_LS_2 |
Moderator (CATT) |
| R4-2220123 |
Topic summary for [105][143] NR_reply_LS_UE_RF |
Moderator (Apple) |
| 11.1 |
Analysis of options for BWP withoutRestriction |
|
| R4-2218161 |
Analysis of options for BWP withoutRestriction |
Apple |
| R4-2218343 |
Analysis of RAN4 options for FG 6-1a support |
Intel Corporation |
| R4-2218414 |
BWP operation without bandwidth restriction |
Qualcomm Incorporated |
| R4-2218439 |
Analysis on the options for BWP withoutRestriction |
CATT |
| R4-2218584 |
Discussion on options for BWP operation without restrictions |
Xiaomi |
| R4-2218631 |
Discussion on options for "bwp-WithoutRestriction" |
CMCC |
| R4-2218780 |
Further discussion on options for BWP operation without restriction |
vivo |
| R4-2218990 |
Further discussion on BWP operation without bandwidth restriction |
OPPO |
| R4-2219563 |
Discussion on options for bwp-WithoutRestriction |
Huawei, HiSilicon |
| R4-2219846 |
Analysis of BWP operation without restriction |
Ericsson |
| R4-2219917 |
Discussion on analysis of options for BWP withoutRestriction |
Nokia Corporation |
| R4-2219928 |
Discussion on BWP operation without BW restrictions |
MediaTek inc. |
| R4-2219929 |
LS response on BWP operation without bandwidth restriction |
MediaTek inc. |
| R4-2220437 |
LS on BWP operation without bandwidth restriction |
Vivo |
| 11.2 |
Study of 2Rx exception for U6GHz |
|
| R4-2218105 |
2RX exception for the 6GHz band |
Apple, Skyworks Solutions Inc., Charter Communications |
| R4-2218641 |
6GHz Rx exception |
CMCC |
| R4-2218844 |
Discussion on 2Rx exception for 6GHz bands |
vivo |
| R4-2219156 |
Discussion on 2Rx exception |
Huawei, HiSilicon |
| R4-2219157 |
CR to 38.101-1: 4 Rx support for n104 |
Huawei, HiSilicon |
| R4-2219821 |
CR for the 2RX exception for the upper 6GHz band |
Apple |
| R4-2220818 |
WF on 2Rx exception for n104 |
AT&T |
| R4-2220827 |
CR to 38.101-1: 4 Rx support for n104 |
Huawei, HiSilicon |
| R4-2220838 |
CR to 38.101-1: 4 Rx support for n104 |
Huawei, HiSilicon |
| 11.3 |
Inconsistency issue for intra-band EN-DC band combinations |
|
| R4-2218118 |
Solutions to resolve intra-band EN-DC combinations issue |
Apple |
| R4-2218119 |
CR to 38.101-3 for corrections on intra-band EN-DC configurations |
Apple |
| R4-2218120 |
CR to 38.101-3 for corrections on intra-band EN-DC configurations |
Apple |
| R4-2218200 |
Further discussion on intra band EN-DC combination inconsistency |
ZTE Corporation |
| R4-2218201 |
CR for TS 38.101-3 on intra-band contiguous EN-DC for DC_(n)41 |
ZTE Corporation |
| R4-2218202 |
CR for TS 38.101-3 on intra-band contiguous EN-DC for DC_(n)41 (Rel-16) |
ZTE Corporation |
| R4-2218203 |
CR for TS 38.101-3 on intra-band contiguous EN-DC for DC_(n)41 (Rel-17) |
ZTE Corporation |
| R4-2218284 |
Discussion on intra-band EN-DC combinations |
Google Inc., CableLabs, Federated Wireless |
| R4-2218285 |
CR for 38.101-3 Rel-16 intra-band contiguous EN-DC band combination |
Google Inc., CableLabs, Federated Wireless |
| R4-2218286 |
CR for 38.101-3 Rel-17 intra-band contiguous EN-DC band combination |
Google Inc., CableLabs, Federated Wireless |
| R4-2218287 |
CR for 38.101-3 Rel-16 intra-band non-contiguous EN-DC band combination |
Google Inc., CableLabs, Federated Wireless |
| R4-2218288 |
CR for 38.101-3 Rel-17 intra-band non-contiguous EN-DC band combination |
Google Inc., CableLabs, Federated Wireless |
| R4-2218829 |
The inconsistency issue for intra-band EN-DC band combinations |
Ericsson |
| R4-2219127 |
Discussion on intrabandENDC-Support |
Xiaomi |
| R4-2219128 |
CR for 38.101-3 Rel-16 to delete the invalid intra-band contiguous ENDC |
Xiaomi |
| R4-2219129 |
CR for 38.101-3 Rel-17 to delete the invalid intra-band contiguous ENDC |
Xiaomi |
| R4-2219412 |
Discussion on intra-band EN-DC combination |
Huawei, HiSilicon |
| R4-2219413 |
[DRAFT] LS on intra-band EN-DC combination |
Huawei, HiSilicon |
| R4-2219583 |
R16 Discussion on IntrabandENDC-Support capability handling |
OPPO |
| R4-2219710 |
Open issues on intra-bandENDC-Support |
Nokia, Nokia Shanghai Bell |
| R4-2220589 |
WF on intra-band EN-DC support capability |
OPPO |
| R4-2220590 |
[DRAFT] LS on intra-band EN-DC combination |
Huawei, HiSilicon |
| R4-2220837 |
LS on intra-band EN-DC combination |
Huawei, HiSilicon |
| 11.4 |
CRs for Canada and US band n77 |
|
| R4-2218121 |
CR to 38.101-1 for updates on mapping of network signaling label for intra-band UL CA |
Apple |
| R4-2218122 |
CR to 38.101-1 for updates on mapping of network signaling label for intra-band UL CA |
Apple |
| R4-2218225 |
Discussion on NS mapping for intra-band CA |
Mediatek India Technology Pvt. |
| R4-2218292 |
Impact of NS mapping issue on n77 US and Canada issue |
Nokia, Nokia Shanghai Bell |
| R4-2218293 |
Introduction of intra band NC UL CA in the n77 frequency range in Canada [n77 Canada] |
Nokia, Nokia Shanghai Bell |
| R4-2218830 |
Clarification of the CA_NS indication and the values for n77 in the US and Canada |
Ericsson |
| R4-2219584 |
R17 Discussion on CA NS mapping |
OPPO |
| R4-2219605 |
CR for TS 38.101-1 to improve the NS mapping for intra-band UL CA (R16) |
Huawei, HiSilicon |
| R4-2219606 |
CR for TS 38.101-1 to improve the NS mapping for intra-band UL CA (R17) |
Huawei, HiSilicon |
| R4-2219607 |
Discussion on NS mapping for intra-band UL CA |
Huawei, HiSilicon |
| R4-2220587 |
Clarification of the CA_NS indication and the values for n77 in the US and Canada |
Ericsson |
| R4-2220588 |
Clarification of the CA_NS indication and the values for n77 in the US |
Ericsson |
| R4-2220717 |
Ad-hoc meeting minutes: RAN task on BWP operation without bandwidth restriction |
Vivo |
| R4-2220831 |
Clarification of the CA_NS indication and the values for n77 in the US |
Ericsson |
| R4-2220832 |
Clarification of the CA_NS indication and the values for n77 in the US and Canada |
Ericsson |
| R4-2220840 |
Clarification of the CA_NS indication and the values for n77 in the US |
Ericsson |
| 11.5 |
Moderator summary and conclusions |
|
| R4-2220078 |
Topic summary for [105][232] RAN_task_RRM |
Moderator (Vivo) |
| R4-2220124 |
Topic summary for [105][144] RAN_task_UERF_part1 |
Moderator (AT&T) |
| R4-2220125 |
Topic summary for [105][145] RAN_task_UERF_part2 |
Moderator (OPPO) |
| 12 |
Revision of the Work Plan |
|
| R4-2218144 |
Motivation of SID revision for LP-WUS |
Apple |
| R4-2218302 |
New WID on Introduction of the Satellite L-/S-Band |
Globalstar, Apple |
| R4-2218303 |
Motivation for a New WID on Introduction of the Satellite L-/S-Band |
Globalstar, Apple |
| R4-2218632 |
Motivation on NR CA band combinations with dual SUL bands in Rel-18 |
CMCC |
| R4-2218633 |
New WID on NR CA band combinations with dual SUL bands in Rel-18 |
CMCC |
| R4-2219722 |
New WID: Introduction of NR TDD band in 1670 - 1675 MHz |
Ligado Networks |
| R4-2219802 |
new WID Additional LTE bands for UE category M1_M2 _NB1_NB2 in Rel-18 |
Ericsson |
| R4-2220126 |
Summary for [105][300] BSRF_Demod_Test_Session |
RAN4 vice-chair (Samsung) |
| R4-2220219 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220261 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220277 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220281 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220285 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220503 |
Discussion on new band for private utility networks |
Anterix |
| R4-2220615 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220616 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220617 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220618 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220619 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220620 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220621 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220622 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220623 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220624 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220625 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220626 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220627 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220628 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220629 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220630 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220631 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220632 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220633 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220634 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220635 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220636 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220637 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220638 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220639 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220640 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220641 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220642 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220643 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220644 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220645 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220646 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220647 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220648 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220649 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220650 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220651 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220652 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220653 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220654 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220655 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220656 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220657 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220658 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220659 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220660 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220661 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220662 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220663 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220664 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220665 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220666 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220667 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220668 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220669 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220670 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220671 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220672 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220673 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220674 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220675 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220676 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220677 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220678 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220679 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220680 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220681 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220682 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220683 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220684 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220685 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220686 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220687 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220688 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220689 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220690 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220691 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220692 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220693 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220694 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220695 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220696 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220697 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220698 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220699 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220700 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220701 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220702 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220703 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220704 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220705 |
(reserved) |
BSRF_Demod_Testing Session |
| R4-2220706 |
(reserved) |
BSRF_Demod_Testing Session |
| 13 |
Any other business |
|
| R4-2219377 |
Discussion on Demod requirements for NCR-MT in Rel-18 |
ZTE Corporation |
| R4-2219599 |
R18 New WI on low band enhancement |
OPPO |
| 14 |
Close of the E-meeting |
|
| R4-2220330 |
(reserved) |
RRM Session |
| R4-2220331 |
(reserved) |
RRM Session |
| R4-2220332 |
(reserved) |
RRM Session |
| R4-2220333 |
(reserved) |
RRM Session |
| R4-2220334 |
(reserved) |
RRM Session |
| R4-2220335 |
(reserved) |
RRM Session |
| R4-2220336 |
(reserved) |
RRM Session |
| R4-2220337 |
(reserved) |
RRM Session |
| R4-2220338 |
(reserved) |
RRM Session |
| R4-2220339 |
(reserved) |
RRM Session |
| R4-2220744 |
(reserved) |
RRM Session |
| R4-2220745 |
(reserved) |
RRM Session |
| R4-2220746 |
(reserved) |
RRM Session |
| R4-2220747 |
(reserved) |
RRM Session |
| R4-2220748 |
(reserved) |
RRM Session |
| R4-2220749 |
(reserved) |
RRM Session |
| R4-2220750 |
(reserved) |
RRM Session |
| R4-2220751 |
(reserved) |
RRM Session |
| R4-2220752 |
(reserved) |
RRM Session |
| R4-2220753 |
(reserved) |
RRM Session |
| R4-2220754 |
(reserved) |
RRM Session |
| R4-2220755 |
(reserved) |
RRM Session |
| R4-2220756 |
(reserved) |
RRM Session |
| R4-2220845 |
(reserved) |
Main Session |
| R4-2220846 |
(reserved) |
Main Session |
| R4-2220847 |
(reserved) |
Main Session |
| R4-2220848 |
(reserved) |
Main Session |
| R4-2220849 |
(reserved) |
Main Session |
| R4-2220850 |
(reserved) |
Main Session |
| R4-2220851 |
(reserved) |
Main Session |
| R4-2220852 |
(reserved) |
Main Session |
| R4-2220853 |
(reserved) |
Main Session |
| R4-2220854 |
(reserved) |
Main Session |
| R4-2220855 |
(reserved) |
Main Session |
| R4-2220856 |
(reserved) |
Main Session |